Subunit output doesn't handle doctest correctly

Bug #707015 reported by Thomas Herve
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
zope.testing
Won't Fix
Undecided
Unassigned
zope.testrunner
Invalid
Undecided
Unassigned

Bug Description

When using the --subunit option of the zope testrunner, I realized that my number of tests dropped down. In the subunit output, I only have that for one doctest file:

test: README_txt
successful: README_txt

The "normal" runner reports one test count for each assertion, instead of one for the whole file. Furthermore, the fact that the file is not prefixed makes all the doctests look the same in the output.

Revision history for this message
Jonathan Lange (jml) wrote :

Actually, the bug is that DocTestCase.id() returns unhelpful information. If we change zope.testing to use str(test), then all of the real unit tests will have bad ids. Perhaps we can do a type-based check to work around the doctest defect.

Revision history for this message
Marius Gedminas (mgedmin) wrote :

This needs to be fixed in zope.testrunner, not zope.testing.

Changed in zope.testing:
status: New → Won't Fix
Revision history for this message
Colin Watson (cjwatson) wrote :

The zope.testrunner project on Launchpad has been archived at the request of the Zope developers (see https://answers.launchpad.net/launchpad/+question/683589 and https://answers.launchpad.net/launchpad/+question/685285). If this bug is still relevant, please refile it at https://github.com/zopefoundation/zope.testrunner.

Changed in zope.testrunner:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.