Lines Matching +full:report +full:- +full:coverage
1 <?xml version="1.0" encoding="UTF-8" ?>
2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-st…
5 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
6 <link rel="stylesheet" href="resources/doc.css" charset="UTF-8" type="text/css" />
7 …<link rel="stylesheet" href="../coverage/jacoco-resources/prettify.css" charset="UTF-8" type="text…
8 <link rel="shortcut icon" href="resources/report.gif" type="image/gif" />
9 <script type="text/javascript" src="../coverage/jacoco-resources/prettify.js"></script>
10 <title>JaCoCo - Ant Tasks</title>
25 and for creating coverage reports from the recorded data. Execution data can
27 <a href="#coverage"><code>coverage</code></a>,
31 created with the <a href="#report"><code>report</code></a> task. For
38 If you want to have line number information included in the coverage reports
46 The JaCoCo distribution contains a simple example how code coverage can be
49 runs an simple Java program and creates a coverage report. The complete
72 <pre class="source lang-xml linenums">
99 <h2><a name="coverage">Task <code>coverage</code></a></h2>
103 <code>testng</code>. To add code coverage recording to these tasks they can
104 simply be wrapped with the <code>coverage</code> task as shown in the
108 <pre class="source lang-xml linenums">
109 <jacoco:coverage>
115 </jacoco:coverage>
118 <jacoco:coverage>
125 </jacoco:coverage>
129 Resulting coverage information is collected during execution and written
136 <code>coverage</code> task can't record coverage information and will fail.
147 The coverage task must wrap exactly one task. While it typically works without
151 <table class="coverage">
162 <td>If set to <code>true</code> coverage data will be collected for the contained task.</td>
173 exists, coverage data is appended to the existing file. If set to
195 the report please configure the <code>report</code> task accordingly.
232 <td><i>auto-generated</i></td>
236 <td>If set to <code>true</code> coverage data will be written on VM
243 <td>Output method to use for writing coverage data. Valid options are:
303 If the <code>coverage</code> task is not suitable for your launch target, you
310 <pre class="source lang-xml linenums">
315 This task has the same attributes as the <code>coverage</code> task plus an
319 <table class="coverage">
331 disabling coverage instrumentation for any tasks that used the value.</td>
340 <td colspan="3"><i>All attributes of the <code>coverage</code> task.</i></td>
353 <pre class="source lang-xml linenums">
365 <a href="#coverage"><code>coverage</code></a> and
373 <table class="coverage">
418 exists, coverage data is appended to the existing file. If set to
434 <pre class="source lang-xml linenums">
445 <table class="coverage">
463 <h2><a name="report">Task <code>report</code></a></h2>
466 Finally different reports can be created with the <code>report</code> task.
467 A report task declaration consists of different sections, two specify the
471 <pre class="source lang-xml linenums">
472 <jacoco:report>
482 <sourcefiles encoding="UTF-8">
487 <html destdir="report"/>
489 </jacoco:report>
493 As you can see from the example above the <code>report</code> task is based
509 This element defines the report structure. It might contain the following
520 files are specified, some report formats include highlighted source code.
528 <table class="coverage">
561 possible and allows to narrow the scope of the report, for example:
564 <pre class="source lang-xml linenums">
581 This way the coverage report can reflect different modules of a software
586 <pre class="source lang-xml linenums">
615 <table class="coverage">
635 Create a multi-page report in HTML format. The report can either be written as
639 <table class="coverage">
650 <td>Directory to create the report in. Either this property or
656 <td>Zip file to create the report in. Either this property or
662 <td>Footer text for each report page.</td>
668 <td><code>UTF-8</code></td>
683 Create a single-file report in XML format.
686 <table class="coverage">
697 <td>Location to write the report file to.</td>
703 <td><code>UTF-8</code></td>
711 Create single-file report in CSV format.
714 <table class="coverage">
725 <td>Location to write the report file to.</td>
731 <td><code>UTF-8</code></td>
739 This report type does not actually create a report. It checks coverage
743 for every package the line coverage is at least 80% and no class is missed:
746 <pre class="source lang-xml linenums">
759 <table class="coverage">
792 <table class="coverage">
833 <table class="coverage">
878 <b>Warning:</b> The preferred way for code coverage analysis with JaCoCo is
879 on-the-fly instrumentation. Offline instrumentation has several drawbacks and
894 <pre class="source lang-xml linenums">
895 <jacoco:instrument destdir="target/classes-instr">
905 <table class="coverage">