Skip to content

Erroneous report of non-executing test statements #10

@nedbat

Description

@nedbat

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.


Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions