Parasoft has announced the release of JTest 8.0, their Java analysis and testing solution. JTest 8.0 introduces a number of new features and improvements, focusing on static code analysis, code review tools, automatic generation of JUnit test cases, Cactus integration, and Bug Detective, which simulates a runtime environment to find bugs. The static code analysis has been improved, adding around 200 new static analyses to bring the number of rules checked up to 700 or so. Hibernate and JavaEE code checks were added in addition to others. The code review tools offer a workflow to enable teams to effectively review code, regardless of geographic location. It's configurable so that who should review the output of someone else can be determined, and users can see their entire code review status at any time. Version control systems (CVS, SVN, Starteam, Clearcase) are integrated with this tool. JTest 8 can also generate test cases during a program run, including coverage statistics. During one demo, for example, a simple RPN calculator was shown, with two types of stacks (LIFO and FIFO) and the four basic mathematic operations. The demo exercised only addition, subtraction, and multiplication on the LIFO stack, and the result was a JUnit test that exactly matched the operations from the user (in order), as well as a report that only 68% of the code had been exercised. QA can use a tool like this to provide exact failure cases to development teams; development teams can use it to generate exact and repeatable test cases for "happy paths" as well as outlying cases. Bug Detective simulates a run through the code to show exception points, including what lines were executed and where the exception occurred. By using runtime analysis rather than static analysis, it can find an entirely different set of bugs than the static analysis tool.

Has anyone used this tool for real unit testing? I saw it on two projects, but it always appeared too complicated and inefficient to use it and we used it just for static code analysis (the tool is very good for this).

JTest is really complicated,but it also provides complete document.The other way round, JUnit is easy to use, but little document. Our company still use JTest6.0 :) Java Book

Hi All, Cisco, Lehman and ISO are all using Parasoft Jtest. “We deployed Jtest as part of our effort to improve development productivity and code reliability. Developers are now required to systematically perform Static Analysis and Unit Testing on new and changed code,” stated Laurent Nicolas, Software Development Manager of Cisco Systems. “Jtest is used to enforce coding standards and to detect and fix errors early in the development cycle. We are constantly looking at ways to improve our bug detection capabilities and are thrilled to explore the new features in Jtest 8.0.” To learn more about Parasoft Jtest 8.0, please visit www.parasoft.com/jtest

What is the best tool out there? There are a myriad of testing tools including this. Mainstream for dev tests I think JUnit rules(a small fraction I think is getting into TestNG) But wanted to know if Fitnesse is really mainstream? http://fitnesse.org/ I like how they do things but uses the wiki language and that may not be handy for a Java guy and hence wanted to know people's experience with Fitnesse.