testtools

Mandatory setUp & tearDown upcalling makes migrating to testtools harder

Bug #1514540 reported by Jonathan Lange
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
testtools
Triaged
Wishlist
Unassigned

Bug Description

Related to #344023

If you're changing the base class of an existing test suite to testtools, then you have to go through and fix every single definition of setUp & tearDown (or do something nasty with private variables).

*Maybe* this is a feature, but it does make adoption harder than it could be.

Revision history for this message
Robert Collins (lifeless) wrote :

We could add way to make the cross check degrade to a warning. E.g. a class variable. Then to migrate you'd make an intermediary base class that set it to warning, and burn it down more slowly.

Changed in testtools:
status: New → Triaged
importance: Undecided → Wishlist
Revision history for this message
Jonathan Lange (jml) wrote : Re: [Bug 1514540] Re: Mandatory setUp & tearDown upcalling makes migrating to testtools harder

Sounds good.
On Mon, 9 Nov 2015 at 18:55, Robert Collins <email address hidden>
wrote:

> We could add way to make the cross check degrade to a warning. E.g. a
> class variable. Then to migrate you'd make an intermediary base class
> that set it to warning, and burn it down more slowly.
>
> ** Changed in: testtools
> Status: New => Triaged
>
> ** Changed in: testtools
> Importance: Undecided => Wishlist
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1514540
>
> Title:
> Mandatory setUp & tearDown upcalling makes migrating to testtools
> harder
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/testtools/+bug/1514540/+subscriptions
>

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.