Skip to content
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

Console and HTML coverage reports differ in branch miss details #342

Closed
nedbat opened this issue Nov 27, 2014 · 2 comments
Closed

Console and HTML coverage reports differ in branch miss details #342

nedbat opened this issue Nov 27, 2014 · 2 comments
Labels
bug Something isn't working report

Comments

@nedbat
Copy link
Owner

nedbat commented Nov 27, 2014

Originally reported by Rowan Pattieson (Bitbucket: rowanpattieson-ipl, GitHub: Unknown)


Using coverage 3.7.1 .

The "BrMiss" field in a console report and the "partial" field in an HTML report sometimes do not agree with one another.

A simple example to demonstrate this (borrowed from Issue #176) is attached as DifferentBranchMissReport.py .

Notice that the console report states there are 16/16 branch misses, whereas the HTML report states there are 0/16 branch misses.

I think the HTML report is correct.
(None of the branches are ever executed, thus they are counted as full misses rather than partial branch misses.)

Also attached are the coverage output, and console and HTML reports.

Commands executed :

#!bash

coverage run --branch DifferentBranchMissReport.py
coverage report > DifferentBranchMissReport_Console.txt
coverage html

@nedbat
Copy link
Owner Author

nedbat commented Nov 27, 2014

Thanks for the detailed report. This issue was fixed last month in changeset bccc40e06c24404e769ef5a5db279f73dadf5113 (bb), though I had neglected to mention it in the CHANGES.txt file. I've updated the CHANGES file in 96aed4a8786d (bb)

@nedbat
Copy link
Owner Author

nedbat commented Nov 27, 2014

Original comment by Rowan Pattieson (Bitbucket: rowanpattieson-ipl, GitHub: Unknown)


Great - didn't manage to discover that it was already fixed in the latest codebase :)

@nedbat nedbat closed this as completed Nov 27, 2014
@nedbat nedbat added major bug Something isn't working report labels Jun 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working report
Projects
None yet
Development

No branches or pull requests

1 participant