Something wrong about branch coverage of class statements · Issue #62 · 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 Jean-Paul Calderone (Bitbucket: exarkun, GitHub: exarkun)

Consider the attached module. Using "coverage run --branch" on it and then "coverage html" produces a coverage report which indicates two partially covered lines.

I would expect that all three methods in the example would be treated the same (ie, either that all three would be marked partially covered, or all three would be marked completely covered).

• Bitbucket: https://bitbucket.org/ned/coveragepy/issue/62
• This issue had attachments: foo.py. See the original issue for details.