Erroneous report of non-executing test statements · Issue #10 · 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

Description

Originally reported by James Bennett (Bitbucket: ubernostrum, GitHub: ubernostrum)

Running coverage on the current tip of my application django-flashpolicies (see http://bitbucket.org/ubernostrum/django-flashpolicies/src/359248e9e4d4/), I get an odd report; coverage doesn't think that the entire view tests file is executing:

Name                                                                             Stmts   Exec  Cover   Missing
--------------------------------------------------------------------------------------------------------------
/Users/jbennett/dev/hg/personal/django-flashpolicies/flashpolicies/tests/views      36     25    69%   28-29, 41-45, 58-59, 72-73

Those lines in the view tests file //are// executing, however, as I can verify by dropping print statements or changing the assertions so that the tests will fail.

The lines reported as missed all have in common that they come immediately after calls to xml.dom.minidom.parseString, but I've no idea why that would cause a problem or whether it's really related.

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