This is the documentation for Clover 3.3. View this page for the

Unknown macro: {spacejump}

of Clover, or visit the latest Clover documentation.

The typical way to use the Clover plugin is by registering a Clover report in your 'project.xml' file, as follows:


Clover Goals




This is the default goal. It compiles the project code with Clover, executes the unit tests and generate Clover reports by calling the clover:report goal.


Compiles the project code with Clover and executes the unit tests.


Execute a single unit test and view the test coverage result directly using the Clover Swing viewer. This is useful if you wish to quickly see the action that a single unit test has on the code it tests.


Generate Clover test coverage reports with Clover. There are 3 possible reports: HTML, XML or Swing. Whether a report is generated is controlled by the properties. The generated reports show exactly what lines of your code were exercised by your tests.


Generate an XML test coverage report with Clover.


Generate an HTML test coverage report with Clover.


Generate a Swing test coverage report with Clover.


Activates Clover, which means that any other plugin calling the Ant javac task will find its code compiled with Clover. This is useful for example to Clover Cactus tests: maven clover:on cactus.


Deactivates Clover, resetting back the normal javac compiler.


Fail the build if the test coverage percentage is below a defined threshold.


Saves a Clover history point that will then be used for generating history reports when the clover:report goal is called.


Merges several Clover databases into one. This goal is meant to be called in the top level master project (multiproject). It is called automatically by the clover:multiproject goal.


Runs Clover on a multiproject and merge the Clover databases.This goal does not generate a report; call clover:report for that or add Clover as a report in your POM.

  • No labels