Precise coverage percentage value · Issue #631 · nedbat/coveragepy (original) (raw)

Skip to content

Navigation Menu

• • GitHub Copilot Write better code with AI
  • GitHub Advanced Security Find and fix vulnerabilities
  • Actions Automate any workflow
  • Codespaces Instant dev environments
  • Issues Plan and track work
  • Code Review Manage code changes
  • Discussions Collaborate outside of code
  • Code Search Find more, search less
• Explore
  • Learning Pathways
  • Events & Webinars
  • Ebooks & Whitepapers
  • Customer Stories
  • Partners
  • Executive Insights
• • GitHub Sponsors Fund open source developers
  • The ReadME Project GitHub community articles
• • Enterprise platform AI-powered developer platform
• Pricing

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Sign up

Appearance settings

Description

Originally reported by Anonymous

Hi,

Situation:

• changing code
• running tests with coverage
• final result: all fine

But that's (sometimes) not true because:

• I'm using coveralls.io and it says (as example) that I have a coverage of 94.708%
• in coverage.py I can say --fail-under=95 and the coverage doesn't fail because it obviously does rounding to an integer.

It's a bit uncomfortable when you run all things locally before you commit your changes but finally fail because of such an issue. It happens to me several times.

I see following essential improvements you could do:

• enable to define precise coverage for --fail-under
• displaying precise coverage

kind regards,

Thomas (mail: thomas.lehmann.private@gmail.com)

• Bitbucket: https://bitbucket.org/ned/coveragepy/issue/631