-
-
Notifications
You must be signed in to change notification settings - Fork 426
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't report missing branches to missing lines. #1065
Labels
Milestone
Comments
I see your point :) |
This is now released as part of coverage 5.5. |
Thank you |
This fix is very much appreciated, thank you both! |
This was referenced Mar 12, 2021
This was referenced May 21, 2021
1 task
1 task
This was referenced Jun 6, 2021
1 task
This was referenced Jul 15, 2021
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a small quality of life suggestion that would make coverage reports easier to read.
Is your feature request related to a problem? Please describe.
Branch coverage can make missing coverage reports difficult to read.
Describe the solution you'd like
Reporting missing branches to missing lines is redundant, if the line didn't get covered then obviously any branches to it didn't either. Omitting these would make coverage reports shorter and easier to read in a lot of cases.
Lets consider one block of 20 lines in one of my files. The missing section of the coverage report looks like this:
496->497, 497, 500->504, 504, 506->510, 510, 512->516, 516
In my humble opinion all of these particular branch reports are unnecessary. Not reporting them would significantly reduce the cognitive load of going through this info and addressing the misses.
497, 504, 510, 516
Of course some branch reports contain useful information. I'm just talking about ones that go to lines that are already going to be reported as missing.
The text was updated successfully, but these errors were encountered: