Description
The <clover-log> task reports coverage information to the console at different levels.
Parameters
Attribute |
Description |
Required |
initstring |
The initstring of the coverage database. |
No; if not specified here, Clover will use the default location (${basedir}/.clover). If you have specified an initstring on the <clover-setup> task, you must ensure that <clover-setup> is called prior the execution of this task. |
level |
Controls the level of detail included in the report. Valid values are summary, class, method, statement |
No; defaults to "summary". |
filter |
comma or space separated list of contexts to ignore when calculating coverage. See Using Coverage Contexts. |
No. |
span |
Specifies how far back in time to include coverage recordings from since the last Clover build. See Using Spans. |
No; defaults includes "all coverage data found". |
Nested elements
<fileset>
Specifies an Ant fileset. Only these files will be used when generating the clover-log messages and coverage data.
<package>
Specifies a named package to restrict the report to. Multiple <package> elements can be specified.
Parameters
Attribute |
Description |
Required |
name |
The name of the package to include. |
Yes. |
<sourcepath>
Specifies an Ant path that Clover should use when looking for source files.
Examples
Prints a summary of code coverage to the console.
Prints a summary of code coverage for the package com.acme.killerapp.core to the console.
Prints detailed (source-level) code coverage information for the package com.acme.killerapp.core to the console.
As above, but catch blocks will not be considered in coverage reporting.
Prints source-level coverage report to the console. Clover will look for source files in the directory /some/other/location.
