testtools-dev team mailing list archive

["Martin \[gz\]" <gzlist@xxxxxxxxxxxxxx>]

Public bug reported:

When the function passed to expectedFailure did not raise an assertion,
bzr used to do:

    self.fail('Unexpected success.  Should have failed: %s' % reason)

With testtools, bazaar now treats that as a success, as jam noted in February:
<https://lists.ubuntu.com/archives/bazaar/2010q1/066898.html>

And in September he pointed out the same thing, but with subunit:
<https://lists.ubuntu.com/archives/bazaar/2010q3/070192.html>

** Affects: bzr
     Importance: Medium
         Status: Confirmed

** Affects: subunit
     Importance: Undecided
         Status: New

** Affects: testtools
     Importance: Undecided
         Status: New


** Tags: regression selftest testtools

** Changed in: bzr
   Importance: Undecided => Medium

** Changed in: bzr
       Status: New => Confirmed

** Also affects: testtools
   Importance: Undecided
       Status: New

** Also affects: subunit
   Importance: Undecided
       Status: New

-- 
An unexpectedSuccess is like a failure not a success
https://bugs.launchpad.net/bugs/654474
You received this bug notification because you are a member of testtools
developers, which is subscribed to testtools.

Status in Bazaar Version Control System: Confirmed
Status in SubUnit: New
Status in testtools: New

Bug description:
When the function passed to expectedFailure did not raise an assertion, bzr used to do:

    self.fail('Unexpected success.  Should have failed: %s' % reason)

With testtools, bazaar now treats that as a success, as jam noted in February:
<https://lists.ubuntu.com/archives/bazaar/2010q1/066898.html>

And in September he pointed out the same thing, but with subunit:
<https://lists.ubuntu.com/archives/bazaar/2010q3/070192.html>