<clover-log> task reports coverage information to the console at different levels.
No; if not specified here, Clover will use the default location (
Controls the level of detail included in the report. Valid values are
No; defaults to "
comma or space separated list of contexts to ignore when calculating coverage. See Using Coverage Contexts.
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".
Since 3.1.6: Specifies which sources shall be taken for calculation. This attribute should be used together with <testSources> nested element.
Valid values are: APPLICATION (business code), TEST (test code), ALL (business + test code).
|No; Default value: APPLICATION.|
|showUnitTests||Since 3.1.6: Show unit tests summary in the report. Must be used with codeType=ALL or codeType=TEST.||No; Default value: false|
|outputProperty||Since 3.1.6: Name of the Ant property in which a clover-log report will be stored, instead of printing it to console.||No;|
Specifies an Ant fileset. Only these files will be used when generating the clover-log messages and coverage data.
Specifies a named package to restrict the report to. Multiple
<package> elements can be specified.
The name of the package to include.
Specifies an Ant path that Clover should use when looking for source files.
Since 3.1.6: Specifies an Ant fileset. These files will be treated as test code (codeType=TEST), all others will be treated as business code (codeType=APPLICATION).
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
Collect coverage data from three directories: src/main/java, src/main/groovy and src/test/java. Test sources are located in: src/test/java. Report coverage for business code only (codeType = APPLICATION), i.e. skip files from src/test/java.
Example for <clover-log showUnitTests="true" code="ALL".../>
By default, log output is written in plain text, for instance:
but if you have a terminal supporting ANSI colors (Linux, for example) you can use -Dansi.color=true property to get a report like this: