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

Report says 100% when it isn't quite there #41

Closed
nedbat opened this issue Jan 7, 2010 · 3 comments
Closed

Report says 100% when it isn't quite there #41

nedbat opened this issue Jan 7, 2010 · 3 comments
Labels
bug Something isn't working report

Comments

@nedbat
Copy link
Owner

nedbat commented Jan 7, 2010

From Gerard Petersen:

When I run an html report (with version 3.2) it tells me it covered 100% when it actually did not. The header of the code report file in question:

Coverage for myapp/views : 100%
514 statements 513 run 0 excluded 1 missing

Roundup wise this is absolutely correct, but technically it isn't. It also says 100% in the overview report (index.html).


@nedbat
Copy link
Owner Author

nedbat commented Jan 7, 2010

This is a rounding issue: the coverage is 99.805%, which rounds to 100%. Perhaps percentages should be truncated rather than rounded.

@nedbat
Copy link
Owner Author

nedbat commented Aug 19, 2010

Original comment by Brandon Rhodes (Bitbucket: brandon, GitHub: brandon)


I concur that percentages should certainly be truncated! :-)

@nedbat
Copy link
Owner Author

nedbat commented Aug 23, 2010

Fixed in <<changeset 9b63ca789328 (bb)>>.

@nedbat nedbat closed this as completed Aug 23, 2010
@nedbat nedbat added major bug Something isn't working report labels Jun 23, 2018
agronholm added a commit to agronholm/coveragepy that referenced this issue Aug 16, 2020
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