Jtest is available in the following editions:

• Professional Edition: A completely integrated tool suite that enables developers/testers to perform automated code analysis (with built-in coding standards/rules and any custom rules developed in the Architect Edition) and automated unit testing (with automatically-generated and user-defined test cases) and in-container testing from the desktop. Tests that scan multiple classes/files/directories can be performed directly from the development environment, with results immediately reported in the GUI for review/repair. Additionally, problems identified by Server Edition tests can be imported into the GUI for review/repair. The Professional edition is intended to be installed and licensed on every developer and tester desktop.
• Architect Edition: Includes the Professional Edition functionality, and adds the RuleWizard module, which enables the creation of custom coding standards/rules using a graphical interface. The Architect Edition is intended for use by an architect or the individual responsible for establishing coding standards for the organization.
• Server Edition: Includes the Architect Edition functionality, and adds support for performing automated code analysis and unit testing as batch or “server” processes. The provided command-line interface can test the complete project code base and be integrated into the automated build process. Results are written to customizable reports, which can be easily accessed by team members and automatically e-mailed to designated recipients. Additionally, developers and testers can import Server Edition test results into the desktop GUI for review/repair.
  The Server Edition also provides:
  • The Team Server module, which enables centralized administration and sharing of coding standards/rule sets, unit testing configurations, and test assets. Team Server is designed for development teams that want to ensure consistency in test practices across the team. When Team Server is implemented team-wide, the architect/lead developer can configure and upload standard team-wide test settings/configurations/files, then Team Server will automatically share them across all team Jtest installations. Team Server may be installed and run on any supported computer system (e.g., one of the developers' workstations, the server hosting a Parasoft Server Edition product, or an independent system).
  • The Code Review module, which automates preparation, notification, and tracking of peer code reviews, addresses the known shortcomings of this very powerful development practice. Jtest automatically identifies updated code by scanning the source control system, matches the code with designated reviewers, and tracks the progress of each review item until closure. With the Code Review module, teams can establish a bulletproof review process—where all new code gets reviewed and all identified issues are resolved.
  • BugDetective, a new static analysis technology that searches a code base for errors which can lead to runtime bugs and application instabilities. By automatically tracing and simulating execution paths that may through even the most complex applications—those with paths that span multiple methods, classes, and/or packages and contain dozens of sequence calls—BugDetective exposes bugs that would be very difficult and time-consuming to find through manual testing or inspections, and would be exponentially more costly to fix if they were not detected until runtime. Using BugDetective, development teams can find, diagnose, and fix classes of software errors that can evade coding standards analysis and/or unit testing.

The following optional licenses are available:

• Jtest Tracer®: Adds the ability to generate functional test cases that capture actual code behavior as a deployed application is exercised. As testers use the application's GUI or a test client (such as Parasoft SOAtest for SOA/Web services or Parasoft WebKing for Web applications) to execute the use cases they want to verify, Jtest Tracer® captures these operations in "positive" JUnit test cases. The result is a library of realistic test cases against which new code can be tested to ensure it meets specifications and does not “break” existing functionality. This license is required to generate test cases with Jtest Tracer®; it is not required to execute Tracer-generated test cases.
• Security: Adds a comprehensive knowledgebase of security issues and guidelines that Jtest can apply when scanning and analyzing source code. When applied, this module will search and identify a broad range of security vulnerabilities, including such issues as improper input handing, malicious code, concurrency issues, improper logging, command injections, improper error handling, string formatting issue, denial of service, authentication, and many more. This module provides the ability to define a security policy that will guide, direct, and enforce secure coding practices in application development.