There's currently no way to know when a dbservice.resetDatabase() has taken effect, which makes it impossible to know when it's safe to start a unit test. Most of the tests don't have a problem here, because they start with an update, and the update is guaranteed to happen after the reset, and they can find out when the update ends. But at least one new test does a lookup immediately (expecting a successful response), and that races with the resetDatabase().
Doesn't seem to be relevant any more after backend rewrites. As far as I can tell resetDatabase is synchronous and immediate now.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.