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 terry.reedy
Recipients ezio.melotti, michael.foord, rbcollins, terry.reedy
Date 2014-09-09.03:58:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1410235095.87.0.0132933806111.issue18232@psf.upfronthosting.co.za>
In-reply-to
Content
You missed my point, which is that tools consuming subunit streams are already able to consider 'no tests found' to be an error. Conversely, when I run the suite on my Windows box, I usually consider only 1 or 2 errors to be success. After unittest reports actual results, the summary pass/fail judgment is only advisory.

To be really flexible and meet all needs for automated adjustment of pass/fail, the new parameter should be function that gets the numbers and at least the set of tests that 'failed'.
History
Date User Action Args
2014-09-09 03:58:15terry.reedysetrecipients: + terry.reedy, rbcollins, ezio.melotti, michael.foord
2014-09-09 03:58:15terry.reedysetmessageid: <1410235095.87.0.0132933806111.issue18232@psf.upfronthosting.co.za>
2014-09-09 03:58:15terry.reedylinkissue18232 messages
2014-09-09 03:58:15terry.reedycreate