➜

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 michael.foord
Recipients eric.araujo, michael.foord, ysj.ray
Date 2010-12-10.10:43:09
SpamBayes Score 2.2065794e-09
Marked as misclassified No
Message-id <1291977791.67.0.079559398485.issue10611@psf.upfronthosting.co.za>
In-reply-to
Content 
At the moment exception handling for setUp / tearDown / testMethod and cleanUp functions are all handled separately. They all have to call addError and as a result we have inconsistent handling of skips, expected failures (etc). There are separate issues for handling expected failures in setUp and skips in tearDown.

I'd like to fix all these issues by moving the exception handling into a single method and unifying the reporting of failure / error / expected failure / skip test. This will fix all these issues and nicely simplify the implementation.
History
Date User Action Args
2010-12-10 10:43:11michael.foordsetrecipients: + michael.foord, eric.araujo, ysj.ray
2010-12-10 10:43:11michael.foordsetmessageid: <1291977791.67.0.079559398485.issue10611@psf.upfronthosting.co.za>
2010-12-10 10:43:09michael.foordlinkissue10611 messages
2010-12-10 10:43:09michael.foordcreate