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="shortcut icon" href="resources/report.gif" type="image/gif" />
8 <title>JaCoCo - FAQ</title>
40 <h3>Does JaCoCo have a plug-in for [Eclipse|Netbeans|Whatever...]?</h3>
56 For coverage report generation all classes within a group must have unique
57 names. You get this error during report generation if JaCoCo is supplied with
59 duplicate classes or create separate reports or report groups for each version.
62 <h3>Source code lines with exceptions show no coverage. Why?</h3>
71 <h3>Why does the coverage report not show line coverage figures?</h3>
73 JaCoCo is based on class files analysis. To calculate line coverage class
78 <h3>Why does the coverage report not show highlighted source code?</h3>
81 highlighting in JaCoCo coverage reports:
85 <li>Source files must be properly supplied at report generation time. I.e.
93 <i>Sessions</i> link on the top right corner of the HTML report and check
96 exact same class file at runtime as for report generation. Note that some
102 <h3>Why are abstract methods not shown in coverage reports?</h3>
104 Abstract methods do not contain code, therefore code coverage cannot be
105 evaluated. Indeed code coverage is recorded for subclasses implementing these
106 methods. The same applies to non-default methods in interfaces.
109 <h3>Can I collect coverage information without stopping the JVM?</h3>
115 <a href="dump-mojo.html"><code>dump</code> Maven goal</a> and the
147 more restrictive then the JVM: JaCoCo expects valid so-called "stackmap
159 <code>-Xshareclasses:none</code>.
172 <h3>Why do I get a <code>StackOverflowError</code> during code coverage analysis?</h3>
184 the <code>-Xss</code> JVM option.</li>
187 <h3>Why do I see classes in the coverage report although I excluded them in the JaCoCo agent config…
196 Report creation is a separate step where all class files which should show up
197 in the report are explicitly provided. Coverage is determined from the
199 this class is shown as not covered because the report generator cannot
204 If you want to exclude classes from the report please configure the
205 respective report generation tool accordingly.