aboutsummaryrefslogtreecommitdiff
path: root/org.jacoco.doc/docroot/doc/faq.html
diff options
context:
space:
mode:
Diffstat (limited to 'org.jacoco.doc/docroot/doc/faq.html')
-rw-r--r--org.jacoco.doc/docroot/doc/faq.html6
1 files changed, 3 insertions, 3 deletions
diff --git a/org.jacoco.doc/docroot/doc/faq.html b/org.jacoco.doc/docroot/doc/faq.html
index 1748b4dc..62d81143 100644
--- a/org.jacoco.doc/docroot/doc/faq.html
+++ b/org.jacoco.doc/docroot/doc/faq.html
@@ -45,13 +45,13 @@
duplicate classes or create separate reports or report groups for each version.
</p>
-<h3>Code with exceptions shows no coverage. Why?</h3>
+<h3>Source code lines with exceptions show no coverage. Why?</h3>
<p>
JaCoCo determines code execution with so called probes. Probes are inserted
into the control flow at certain positions. Code is considered as executed
when a subsequent probe has been executed. In case of exceptions such a
- sequence of instructions is aborted somewhere in the middle and not marked as
- executed.
+ sequence of instructions is aborted somewhere in the middle and the
+ corresponding line of source code is not marked as covered.
</p>
<h3>Why does the coverage report not show line coverage figures?</h3>