Produces an XML report of Code Coverage for the given coverage database.
Note: in Clover 3.1.x and older a class was named com.cenqua.clover.reporters.xml.XMLReporter.
-i, --initstring <file>
The initstring of the coverage database.
-o, --outfile <file>
The file to write XML output to.
Forces a report to be generated, even if there is no coverage data. Defaults to '
Switch logging level to debug.
-f, --filter <string>
Comma or space separated list of contexts to ignore when generating coverage reports. Most useful one is "catch".
Specifies whether or not to include coverage attributed to a test that has failed. If omitted, failed test coverage is not included. Default setting is 'false'.
Include source-level coverage info.
-s, --span <interval>
Specifies how far back in time to include coverage recordings from. . See Using Spans. Default includes "all coverage data found".
|-si, --showinner||Since 3.2.0: Show inner functions in the report (like a lambda function inside a method).|
|-sl, --showlambda||Since 3.2.0: Show lambda functions in the report.|
|-tc, --threadcount <int>||Number of additional threads to be allocated to report generation. Default is 0.|
-t, --title <string>
Switch logging level to verbose.
@since Clover 3.1.12: The XMLReporter.main() calls System.exit() and returns non-zero return code in case of error during XML report generation.
XMLReporter provides a simple API that accepts an array of strings representing the command line arguments and returns an integer result code. The following fragment illustrates use of the API:
Read coverage for the Clover database "clover.db", and produce a report in the file "coverage.xml"
Produce the same report as above, but include source-level coverage information, and a report title.