31 March 2010

Atlassian presents Clover 3.0

Clover 3.0 is a major release which adds Groovy support for Ant, Maven 2 and Grails. We also offer the new Clover-for-Grails plugin that allows you to use Clover's code coverage capabilities directly inside your Grails project. Furthermore, we add a new per-test coverage viewer and completely new dashboard view to Eclipse.

Upgrading to Clover 3.0 is free for all customers with active Clover software maintenance at the date of launch.

Highlights of Clover 3.0:

Thank you for your feedback:

Your votes and issues help us keep improving our products, and are much appreciated.


Clover 2.6 can be downloaded from the Clover Download Centre. Before upgrading, please refer to the relevant documentation:

Highlights of Clover 3.0

 

Groovy Support for Ant, Maven 2 and Grails

Clover 3.0 Ant and Maven 2 plugins now provide support for Groovy. Most Clover-for-Ant tasks will now work on Groovy code and the Clover-for-Maven 2 plugin now supports Groovy code compilation and report generation.

Read more: Clover-for-Ant Upgrade Guide and Upgrade Notes for Clover-for-Maven 2 Groovy Integration.

(info) Unless otherwise indicated, all tasks described in the Clover-for-Ant User's Guide work with Groovy code.

Groovy Code Coverage Reporting

Clover's reporting features support Groovy code, which includes per-test coverage and other reporting features available in Ant and Maven 2.

Furthermore:

  • Clover will only report a line that contains Groovy's safe operator as covered if the check evaluated to both true and false.
  • Clover also supports filtering specified Groovy methods.

Screenshot: Clover Groovy Code Coverage

Screenshot: Clover Filtering Specified Groovy Methods

 

New Clover-for-Grails Plugin

Clover 3.0 now incorporates a new plugin for the Grails web application development framework. Grails project developers can now test their Groovy code using Clover to generate coverage reports.

The Clover-for-Grails plugin is very easy to install and upgrade, with multiple installation options that can be issued from a single Grails command. Upgrading is as easy as reinstalling the Clover-for-Grails plugin.

You can configure the Clover-for-Grails plugin on the command line or by including Clover-for-Ant-based (Gant) instructions directly inside the BuildConfig.groovy file.

Read more: Clover-for-Grails, Clover-for-Grails Installation and Upgrade Guide

Screenshot: Clover Report Dashboard of a Grails Project

 

Per-Test Coverage Viewer for Eclipse

The Clover-for-Eclipse plugin includes a new inline per-test coverage viewer. Hovering over the gutter now displays a pop-up with a list of tests that hit that line. Clicking on a test will take you directly to the test source code.

Screenshot: New Clover-for-Eclipse per-test coverage pop-up

 

New Dashboard View in Eclipse

For the first time, the Clover Report Dashboard is now available in Eclipse!

 

Updated Tutorial with Groovy Code

The existing 'Money Demo' tutorial (located in CLOVER_HOME/tutorial) has been updated with additional Groovy code for Ant and Maven 2. The Ant (build_completed.xml) and Maven 2 (pom_completed.xml) tutorial solution files contain examples of Groovy integration.

For Ant builds, your Groovy code will automatically be compiled if the GROOVY_HOME environment variable has been set and points to the location of your Groovy directory.

Read more: Tutorial - Using Clover with Ant and JUnit

 

Other Enhancements and Improvements

Clover-for-Maven 2

The clover2:check task now has two new parameters: methodPercentage and conditionalPercentage. These parameters allow you to set target percentages that define when to fail the build for methods and conditions, respectively.

(info) Be aware that these will only be used if maven.clover.targetPercentage has been set.

For more information, please refer to the Clover-for-Maven 2 User's Guide.

Clover XML Reports

The Clover XML report now includes test results and Clover ships with an XML schema (XSD) for these reports.

 

Over 50 bug fixes and improvements

See the changelog for details.