tests: transform "migrate" testsuite into "reset database" testsuite #763
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This was my initial goal, when I split the test suite: to have a "reset database" testsuite, and a main test suite.
Another cool thing is that I've moved all the tests related to "global story" here. Each time I have some complex stuff to debug in the main testsuite, I always deactivate the global stories, because it creates some noise (extra pass in
create()
method, for example)something I'm wondering is maybe we can now remove some permutations for the main testsuite in the CI. maybe remove sqlite and pgsql permutations, always use dama... WDYT?