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

Unknown macro: {spacejump}

of Clover, or visit the latest Clover documentation.

Skip to end of metadata
Go to start of metadata

To get Clover 2 integrated into your build as quickly as possible, follow these simple steps.

(warning) These instructions require Ant 1.7 or later.

  1. Download the clover.jar and save it in your home directory.
  2. Add the following lines to your build.xml file:
    <taskdef resource="cloverlib.xml" classpath="${user.home}/clover.jar"/>

    (info) Note that this will not work within an Ant target. It must be at the top level of the build file.

  3. Add the clover.jar to your test-time classpath:
    <junit fork="true" forkmode="once">
        <pathelement location="${user.home}/clover.jar"/>

  4. The following targets will then be available to you:

    (info) These are available also by running `ant -projecthelp`.

    Target Name



    Runs clover.clean, with.clover, test, from a single target.


    Deletes the clover database and the




    Generates an HTML and XML report to





    Same as clover.current, however a history report will also be created, using the historypoints in



    Saves a history point to



    Enables Clover on this build


    Saves a snapshot file to assist with unit test optimization

For more instructions about using targets, see the Clover Target Reference.
Any ${} properties may be defined on the command line, for example:


  1. If you have a target already called "test" you can simply run
    ant clover.all

    Otherwise, run the following:
    ant with.clover

    Alternatively, define a property called "" whose value is the name of your test target.

That concludes the Ant two-line integration. You should now be set up to run Clover on your Ant builds and start taking advantage of Clover's advanced code coverage analysis.

Need more information? Find it in the Clover QuickStart Guide.

  • No labels