tests report multiple results
Bug #335816 reported by
Robert Collins
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| testtools |
Fix Released
|
Wishlist
|
Robert Collins | ||
Bug Description
I may be wrong, but it looks like
class Foo(TestCase):
def test_bar(self):
def tearDown(self):
raise "havoc"
will result in the TestResult object having both addFailure and addError called on it. That seems undesirable.
| Changed in testtools: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| Changed in testtools: | |
| importance: | Medium → Wishlist |
Revision history for this message
| Robert Collins (lifeless) wrote | #1 |
| Changed in testtools: | |
| status: | Confirmed → Fix Released |
| assignee: | nobody → Robert Collins (lifeless) |
| milestone: | none → next |
To post a comment you must log in.
This is a problem because few, if any, TestResult objects understand
startTest
addFailure
addFailure
stopTest
generally their UI framework blows up, in various ways, on the second addFailure.