Integration tests: residual objects in object database

[Garfonso]

Might be only local, not 100% sure, yet.

I can definitively see enums (room & function) that are still present from previous tests and cause errors (because certain object still is member of an enum, that should not be there at all).

I once saw a state object still present for all tests and even after testing was done I could find it in objects.jsonl file.

From what I understood databases should be empty (or at least at some defined status) at the beginning of each test.

[Garfonso]

ok, problem was / is related to residual test directory locally from somehow not clean stopped test run (i.e. before first test run there already was a objects.jsonl file which contained objects and that was used as backup to restore to, if I understand the code correctly). :-/ Sorry.

[AlCalzone]

Hmm, let me check if we should clear the DB before the first test to avoid this.