In addition to helping developers automate best practices in their Java code, Jtest is part of a team-wide automated error prevention product suite that standardizes and manages an application across the entire development organization. Clients using Jtest includes, Bank of America, Cisco, Hertz and IBM.

"Business requirements have created an urgency among Java development teams to prove that they are delivering secure, quality code. Jtest 6.0 provides these teams early visibility into code quality and introduces a collaborative workflow that extends their ability to leverage testing assets across development environments," said Bill Leavy, vice president of marketing at Parasoft. "Development teams can now shift from simple task automation using individual point tools to a the unified process available in Parasoft's product suite."

Java code provides the application logic for everything from Web services, to traditional Web applications, to desktop applications, to embedded devices. Reliability, security and performance problems can impact functionality, as much as Java coding errors. Jtest 6.0 introduces a collaborative workflow that allows enterprise development teams to more effectively produce millions of lines of secure and reliable code. It also extends the development team's capability to leverage testing assets across the development environment.

Jtest 6.0 includes automatic JUnit test case generation; more built-in and customizable development rules; goal-based workflow and a new object repository. New capabilities Parasoft outlined includes, increased coverage for complex code with configurable scenarios in JUnit framework; more realistic tests in user defined and automatic test cases via a new object repository; quick creation of unit test cases with a flexible test case editor; over 500 built-in Java development rules; ability to test .jsp files, and a security module that delivers over 100 security vulnerability rules.

Java development teams use Jtest to produce more reliable, secure and easier to maintain Java code that is less likely to experience functional problems. Development teams spend less time finding and fixing errors due to the automated nature of Jtest. Regardless of a team's size, organization, projects or development methodology releases are more likely to occur on time, on budget and with the expected functionality.