This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author chris.jerdonek
Recipients asvetlov, brett.cannon, chris.jerdonek, docs@python, eli.bendersky, eric.araujo, ezio.melotti, georg.brandl, r.david.murray, sbt, terry.reedy, v+python
Date 2012-09-13.16:58:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1347555506.62.0.0226280736311.issue15629@psf.upfronthosting.co.za>
In-reply-to
Content
Attached is a file of doctest statistics (counts of example failures, exceptions, and successes) for almost every file in the Doc directory when running the doctests with vanilla doctest.

I did this to get a sense of which files it would be easiest to get into a "passing" state, and to see how many files actually have doctest examples.

It was actually non-trivial to get fine-grained test result data like this because doctest only exposes the ability to create a unittest.TestCase for each file (i.e. an entire file either registers as a success or failure).  From the API, you can't get results down to the level of individual doctest examples.

See also issue 15938 that I recently created which would be a small step in this direction (getting a total example count independent of successes and failures).
History
Date User Action Args
2012-09-13 16:58:28chris.jerdoneksetrecipients: + chris.jerdonek, brett.cannon, georg.brandl, terry.reedy, ezio.melotti, eric.araujo, v+python, r.david.murray, eli.bendersky, asvetlov, docs@python, sbt
2012-09-13 16:58:26chris.jerdoneksetmessageid: <1347555506.62.0.0226280736311.issue15629@psf.upfronthosting.co.za>
2012-09-13 16:58:26chris.jerdoneklinkissue15629 messages
2012-09-13 16:58:25chris.jerdonekcreate