Jtest continues its trek toward code-testing supremacy
Version 8 of Parasoft's Java test tool sports impressive BugDetective analysis features
Most of the tests created are based on a JUnit foundation, but Jtest adds support for Cactus, a JUnit-extending framework from the Jakarta Project that recognizes just about every server-side component there is; HttpUnit, a general-purpose Web-testing framework that mimics a user executing from a browser; Springs; Struts; and other platforms.
Other improvements cover the entire Jtest tool collection. For example, past versions of Jtest generated tests at the class level. Now you can set filters on test creation so that tests are generated for, say, only public methods, ignoring private and protected methods.
Such “fine-tuning” of tests goes even further if Jtest is connected to a version control system. In that case, you can do things such as specify that Jtest create tests for only source code modified since a given date and restrict test generation to new code.
Bug Detective is perhaps Jtest 8’s best addition. It can — if you have the time — be configured to exhaustively explore an application’s execution paths. The default “exploration depth” is set to about 100 sequentially executed lines, but that can be adjusted to something much larger. And in this age of copious available processor cycles, it wouldn’t be unthinkable to devote a small farm of test systems to simply sit around all night, exploring your Java source, and maybe finding something you wouldn’t have expected. That’s where Jtest shines brightest.