Message 193796 - Python tracker

➜

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	docs@python, ezio.melotti, michael.foord, py.user, terry.reedy
Date	2013-07-27.20:56:14
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1374958574.55.0.744145892127.issue18566@psf.upfronthosting.co.za>
In-reply-to

Content
I re-ran with setUp 'raise' changed to 'pass' to see the effect of raise AssertionError or unittest.SkipTest in tearDown and indeed the test fails or skips even then. I suggest adding ', other than AssertionError or SkipTest,' just after 'method'. The same is true of test_xxx methods. A slight anomaly is that AssertionError in test_nothing and SkipTest in tearDown results in "FAILED (failures=1, skipped=1)", which is not really a skip. For setUpClass and setUpModule, AssertionErrors are errors, not failures, while SkipTest works everywhere.

I re-ran with setUp 'raise' changed to 'pass' to see the effect of raise AssertionError or unittest.SkipTest in tearDown and indeed the test fails or skips even then. I suggest adding ', other than AssertionError or SkipTest,' just after 'method'. The same is true of test_xxx methods.

A slight anomaly is that AssertionError in test_nothing and SkipTest in tearDown results in "FAILED (failures=1, skipped=1)", which is not really a skip.

For setUpClass and setUpModule, AssertionErrors *are* errors, not failures, while SkipTest works everywhere.

History
Date	User	Action	Args
2013-07-27 20:56:14	terry.reedy	set	recipients: + terry.reedy, ezio.melotti, michael.foord, docs@python, py.user
2013-07-27 20:56:14	terry.reedy	set	messageid: <1374958574.55.0.744145892127.issue18566@psf.upfronthosting.co.za>
2013-07-27 20:56:14	terry.reedy	link	issue18566 messages
2013-07-27 20:56:14	terry.reedy	create