Changes by Tim Cuthbertson :
--
nosy: +gfxmonk
___
Python tracker
<http://bugs.python.org/issue15112>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Tim Cuthbertson :
--
nosy: +gfxmonk
___
Python tracker
<http://bugs.python.org/issue9334>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Tim Cuthbertson :
This patch adds the behaviour that when a unittest.failureException is
thrown in a TestCase's tearDown method, the test case is added to the
failures list (instead of the errors list, and only when the test case
body has passed successfully).
In
Tim Cuthbertson added the comment:
updated patch: made the test method name unique (oops), and added the
specific test case where both test body and tearDown raise failure
exceptions. This patch supercedes the original (v0)
--
Added file: http://bugs.python.org/file13388/unittest-fail
Tim Cuthbertson added the comment:
I agree that this is not normally the point of tearDown methods.
However, allowing it reduces repetition when you want to verify that
some invariant is not violated by any test.
I also think that as far as the test writer is concerned, an assertion
error is a
Tim Cuthbertson added the comment:
In my mind, an error means something is wrong. A failure just means a
test case hasn't been implemented yet, or has regressed. For me it's
misleading to have an AssertionError reported as a failure. It's not as
if changing the reporting in this
