To get Clover integrated into your build as quickly as possible, follow these simple steps.
Add the following lines to your build.xml file:
<taskdef resource="cloverlib.xml" classpath="${user.home}/clover.jar"/>
<clover-env/>
|
Note that this will not work within an Ant target. It must be at the top level of the build file.
Add the clover.jar to your test classpath:
<junit fork="true" forkmode="once">
<classpath>
<pathelement location="${user.home}/clover.jar"/>
</classpath>
</junit>
|
If you have a target already called "test" you can simply run
ant clover.all |
Otherwise, run the following:
ant with.clover your.test.target clover.report |
Alternatively, define a property called "test.target" whose value is the name of your test target.
Complete! 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.
By calling <clover-env/>, the following targets becomes available to you:
|
These are available also by running `ant -projecthelp`.
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
Need more information? Find it in the Clover QuickStart Guide. |