ASSERT-KTH
Lines before exception are not included in the coverage result
Source code lines with exceptions show no coverage. Why?
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 the corresponding lines of source code are not marked as covered.
From: https://www.jacoco.org/jacoco/trunk/doc/faq.html
This means that there are some cases (such as the ones identified in https://github.com/SpoonLabs/nopol/pull/220#issuecomment-926641347) where lines just before an exception are not included in the coverage result from Jacoco, and consequently on the final Flacoco result.
To fix this, we would have to rewrite the probe insertion/analysis part of Jacoco to add a probe at the beginning of each line. This would be a fundamental change in the way Jacoco works.
Alternatively, we could consolidate and use https://github.com/JetBrains/intellij-coverage, which does work for these cases
We could also reverse engineer the bytecode control flow probe placement of JaCoCo and post-process class files when we do the stack-trace parsing.
We will try to parse the source code of classes present in stack-traces and meant to be included in the coverage computation, such as to include lines in the block of the line that threw the exception.
It potentially minimizes this limitation.