Coverage report from unit tests is inaccurate

3 views (last 30 days)
Micah Fry
Micah Fry on 16 Jun 2021
Commented: Micah Fry on 17 Jun 2021
Using the matlab.unittest.plugins.CodeCoveragePlugin with class-based unit tests produces coverage reports that are not always accurate. I see them repeatedly (but not always) occur when function handles are split across multiple lines. The following image provides an example (code to reproduce it is attached).
The "missed line" goes away if you replace isequal(x) with x == x in line 4. Also, if you just remove the ellipsis and have the function handle defined entirely on one line, the report does not display a "missed line."

Answers (1)

Neeraj Badamikar
Neeraj Badamikar on 17 Jun 2021
Hello Micah,
Thank you for reporting this. We've had a few other users reporting about this issue and we are working on addressing it.
One possible solution we're looking at is to report code coverage on entire MATLAB statements as opposed to lines. That would ensure that a statement like this -
function_handle_with_wrapping_line_for_isequal = @(x) ~isequal(x, x) || ...
isequal(x, x);
would either be marked as covered or not covered in entirety.
Is that something that you would find useful?
Micah Fry
Micah Fry on 17 Jun 2021
Is there a bug tag I can keep track of for this issue? It looks like this may be related to another question (

Sign in to comment.




Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by