Coverage report from unit tests is inaccurate

2 次查看（过去 30 天）
Micah Fry
Micah Fry 2021-6-16
评论： Micah Fry 2022-3-18
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."

请先登录，再回答此问题。

回答（1 个）

Neeraj Badamikar
Neeraj Badamikar 2021-6-17
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?
Regards,
Neeraj
  4 个评论
显示 2更早的评论
Micah Fry
Micah Fry 2021-6-17
Is there a bug tag I can keep track of for this issue? It looks like this may be related to another question (https://www.mathworks.com/matlabcentral/answers/575389-some-lines-missed-in-code-coverage-report).

请先登录，再进行评论。

类别

在 Help Center 和 File Exchange 中查找有关 Write Unit Tests 的更多信息

标签

产品


版本

R2020b

Community Treasure Hunt

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

Start Hunting!

Translated by