unittest.expectedFailure not treated as unexpectedsuccess

turns out that it works as desired when using @unittest2.expectedFailure

"unittest.expectedFailure not treated as unexpectedsuccess" confuses me a bit. Guessing it means that tests which are decorated with "unittest.expectedFailure" and _pass_ are not treated as unexpectedsuccess.

yes, and it's an interoperability problem with the *unittest* decorator, as
opposed to unittest2 and/or whatever testtools provides.

On Thu, Nov 19, 2015 at 5:56 AM, Jonathan Lange <email address hidden> wrote:

> "unittest.expectedFailure not treated as unexpectedsuccess" confuses me
> a bit. Guessing it means that tests which are decorated with
> "unittest.expectedFailure" and _pass_ are not treated as
> unexpectedsuccess.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1417803
>
> Title:
> unittest.expectedFailure not treated as unexpectedsuccess
>
> Status in testtools:
> Triaged
>
> Bug description:
> when running "testr run --subunit -- <tests> | <my parser>"
>
> in show_outcome() implemented by my parser, the test['status'] is
> failed, not uxsuccess
>
> The test class inherits from testtools.TestCase, and the test method
> was marked with @unittest.expectedFailure
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/testtools/+bug/1417803/+subscriptions
>

Ah, gotcha. Would you mind providing a minimal example test and a minimal example parser?