Testtools.TestCase eats DBBackup.save method
Bug #1255178 reported by
Ed Cranford
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
Triaged
|
Low
|
Unassigned |
Bug Description
For some reason in our unittests, the save method belonging to trove.backup.
I suspect it's a matter of timing or test ordering.
Asserting that the save method is not None at several points in the unit tests have shown that this change happens within the body of at testcase's setUp method
At present one workaround is to simply save the save method, and then restore it immediately in setUp. This is demonstrated in conductor's test_methods unittests.
Changed in trove: | |
status: | New → Triaged |
importance: | Undecided → Low |
To post a comment you must log in.