diff options
| author | Marc R. Hoffmann <hoffmann@mountainminds.com> | 2012-11-13 23:03:55 +0100 |
|---|---|---|
| committer | Marc R. Hoffmann <hoffmann@mountainminds.com> | 2012-11-13 23:03:55 +0100 |
| commit | f6787ed6b196b4d75e8ef238a049c498f13e603e (patch) | |
| tree | 56e28aee5daa7012cd49e19856659063bb96b3c2 | |
| parent | fa0c8a1883b6e8733444eb7b634395a6fcce1d84 (diff) | |
| download | jacoco-f6787ed6b196b4d75e8ef238a049c498f13e603e.tar.gz | |
Another FAQ entry.
| -rw-r--r-- | org.jacoco.doc/docroot/doc/faq.html | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/org.jacoco.doc/docroot/doc/faq.html b/org.jacoco.doc/docroot/doc/faq.html index de5ef335..c9bfee8d 100644 --- a/org.jacoco.doc/docroot/doc/faq.html +++ b/org.jacoco.doc/docroot/doc/faq.html @@ -37,6 +37,15 @@ duplicate classes or create separate reports or report groups for each version. <p> +<h3>Code with exceptions shows 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. +</p> + <h3>Why does the coverage report not show line coverage figures?</h3> <p> JaCoCo is based on class files analysis. To calculate line coverage class |