14 February 2008
Clover 2.1 allows you to tailor your coverage reporting even more closely to your needs. Configurable risk metrics let you choose an algorithm that matches your definition of a project risk. 'Coverage Clouds' are now available for every individual package. Building on the per-test coverage that was introduced in Clover 2.0, in Clover 2.1 reports from merged databases now include per-test coverage data. Additionally, a whole range of advanced charting options are available. Clover historical reports are now much more configurable, especially the charts and movers section. You can now customise which data gets shown, where.
Upgrading to Clover 2.1 is free for all customers with active Clover software maintenance at date of launch.
Clover 2.1 can be downloaded from the Clover Download Centre. Before upgrading, please refer to the relevant documentation:
You can now see what tests hit what code, even when generating combined reports across multiple databases.
Read more
Coverage clouds are now available at the package level, allowing you to compare classes within a specific package. This is specifically aimed at large projects, which have multiple developers working in different packages.
New charts have been added to historical reports. You now have complete control over series in the charts.
Movers are classes which have either gained coverage or lost coverage. You can now define multiple movers in a report, allowing you to easily spot them. For example, you could now show classes which have changed in the last day, as well as classes that have changed in the last week.
The new Clover Expression Language allows you to combine metrics in interesting ways, to derive your own original metric.
The new SUM Metric is a new column that provides a risk ranking, in much the same way that Crap4J does.