Reduce need for force_dirty_database in tests
Bug #476297 reported by
Jeroen T. Vermeulen
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
We just fixed bug 476218: test B fails because test A runs a script but fails to tell the test setup that the database is dirty.
Could/should we avoid the need for this? For instance we could make run_script call force_dirty_
| affects: | launchpad → launchpad-foundations |
| Changed in launchpad-foundations: | |
| importance: | Undecided → Low |
| status: | New → Triaged |
To post a comment you must log in.
