Partial Coverage Calculation Only on Path 0
See original GitHub issueIs there a particular reason Coverage Gutters only marks lines as partially covered when the else
path, or path 0
has no hits? Shouldn’t it check that all paths for the branch condition have hits and mark it as partial
if any of them do not?
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Partial coverage of a return statement in C++/CLI
) are marked in orange - partially covered. I have no idea why is it partially covered instead of fully covered, and this...
Read more >Testing: Dataflow Coverage
(d) List a minimal test set that satisfies all-defs coverage with respect to x (Direct tours only). Use the given test paths. (e)...
Read more >Requirement Coverage - IBM
The test case then only partially covers the requirement - a dependency stereotyped partially on the requirement is added to the TestScenario generated...
Read more >Code Coverage Tutorial: Branch, Statement, Function Coverage
This comprehensive tutorial explains what is Code Coverage in Software Testing, why we need it, its types, benefits, and drawbacks.
Read more >Using Code Coverage in batchmode
-coverageResultsPath (optional), to set the location where the coverage results and report are saved to. The default location is the project's path. - ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@hunterjm closing this one for now but I did include eefce5d in the upcoming release (you can also find the .vsix file in the tag release if you want to see it early).
@hunterjm ahh I see now thanks for the extra info, I will fix this in the 2.0 release 😄