Vanward beefs up Java project tracking
Convergence adds source-metric, test-tracking muscle to Maven-based projects
You may also view profiles of individual classes. The profile screen includes a link to graphical information that plots class size (source code lines) against build number, revealing how the class has grown across time. It also shows coverage percentages achieved by tests associated with the class, showing how well the unit tests’ coverage has kept up with the growth of the class’ source.
If you descend into data related to the associated unit-testing code by clicking the “test packages” link beneath a project name, Convergence brings you to a page that lists all the application’s test packages.
Here, Convergence presents a summary of test successes and failures for each package from the most recent build. You can drill down along two branches. Click the test package name to view a list of classes within the package and see each class’s test successes and failures. Click the historical-information icon to view the package’s successes and failures for all past builds.
Because Convergence relies on several technologies, its installation is actually a combination of installations. I doubt, however, that anyone who has used Maven will have any difficulty setting up MySQL, Tomcat, or Convergence. Installing Convergence’s dashboard requires no more effort than moving a WAR file into Tomcat’s application-deployment directory.
Although the version I tested was for Java only, Convergence also supports C# and C++ .Net, although the feature set is not as robust as it is with Java. However, Convergence engineers say the .Net capabilities should be on par with Java by mid-to-late 2005.
Initially, Convergence can be a bit daunting. There are so many ways to explore the captured data that new users will likely find themselves groping. The documentation could use some work, too; its scattered organization left me wondering if the document writers weren’t groping as well.
However, Convergence organizes enough data in enough ways so that almost any Java developer will find it a worthwhile project-tracking adjunct to Maven. You just need to spend some time getting familiar with the lay of the land -- it will be worth it.