To get Clover 2 integrated into your build as quickly as possible, follow these simple steps.
These instructions require Ant 1.7 or later.
<taskdef resource="cloverlib.xml" classpath="${user.home}/clover.jar"/> <clover-env/>
<junit fork="true" forkmode="once"> <classpath> <pathelement location="${user.home}/clover.jar"/> </classpath> </junit>
Target Name |
Description |
---|---|
clover.all |
Runs clover.clean, with.clover, test, clover.report from a single target. |
clover.clean |
Deletes the clover database and the ${clover.dest} directory. |
clover.current |
Generates an HTML and XML report to ${clover.dest} using ${project.title} . |
clover.report |
Same as clover.current, however a history report will also be created, using the historypoints in ${clover.project.historydir} . |
clover.save-history |
Saves a history point to ${clover.project.historydir}
|
with.clover |
Enables Clover on this build |
clover.snapshot |
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:
-Dclover.project.historydir=/home/clover/historydir/
ant clover.all
ant with.clover your.test.target clover.report
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.