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 rbcollins
Recipients hpk, michael.foord, ncoghlan, r.david.murray, rbcollins
Date 2014-10-23.07:54:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1414050857.27.0.11484573086.issue10548@psf.upfronthosting.co.za>
In-reply-to
Content
My take on this, FWIW, is that any methods in the under-test API - setUp, tearDown, test_* and anything registered via addCleanup should all support the same protocol as much as possible, whatever it is.

That is, raising a skip in setUp should skip the test. raising a skip in tearDown should skip the test, and raising a skip from a cleanup should skip the test.

This is complicated by the case where some code is called after exceptions- teardown and cleanups. Thats fairly straight forward: errors are higher precedence than failure than skips than anything which resolved as a pass.
History
Date User Action Args
2014-10-23 07:54:17rbcollinssetrecipients: + rbcollins, ncoghlan, r.david.murray, michael.foord, hpk
2014-10-23 07:54:17rbcollinssetmessageid: <1414050857.27.0.11484573086.issue10548@psf.upfronthosting.co.za>
2014-10-23 07:54:17rbcollinslinkissue10548 messages
2014-10-23 07:54:16rbcollinscreate