Define the expected state of the database between test cases
|Reported by:||Aymeric Augustin||Owned by:||Aymeric Augustin|
|Has patch:||yes||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
As pointed out in this commment, the fix for #20483 doesn't use the correct set of content types and permissions, because the database is flushed at the end of the test case, not at the beginning. That behavior was introduced in #18271.
The goal of this ticket is to find a good compromise between:
- making the state of the database between test cases as deterministic as possible,
- preserving the optimization of #20483,
- not introducing backwards incompatibilities,
- minimizing the amount of changes — we're after 1.6 alpha.