zope.testrunner does not handle unexpected test successes but it claims to do so

[Michael Howitz]

Python 2.7 added the concept of expectedFailures to unittest.
See http://www.voidspace.org.uk/python/articles/unittest2.shtml#more-skipping

When a test decorated with @unittest.expectedFailure does not raise an exception this test is counted as success when running the tests with zope.testrunner.

It should be handled separately besides failures and errors.

Meanwhile `addUnexpectedSuccess` could be set to None on zope.testrunner.runner.TestResult. Although this produces a Warning it counts the unexpected success as failure. So it does not get counted as success as currently.

[Michael Howitz (mh-gocept)]

Released in zope.testing 3.9.6 resp. zope.testrunner 4.0.1

[Lennart Regebro (regebro-gmail)]

Setting addUnexpectedSuccess to None gives you a completely misleading and useless error message, as the message you get is "TypeError: 'NoneType' object is not callable". I'll revert this change.

[Michael Howitz (mh-gocept)]

Am 14.03.2011 um 20:00 schrieb Lennart Regebro:
> Setting addUnexpectedSuccess to None gives you a completely misleading
> and useless error message, as the message you get is "TypeError:
> 'NoneType' object is not callable". I'll revert this change.

Which Python version do you use?
Python 2.7 has a test to show at behaves correct with the fix.

Yours sincerely,
--
Michael Howitz · <email address hidden> · software developer
gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany
http://gocept.com · tel [phone] · fax [phone]
Zope and Plone consulting and development