chore: Integration tests setup db once #2118
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Integration tests success for deb0145ceb34b423a6bb3ecb3cd508c48e07f38c |
|
Integration tests success for 49dccd9ef6a6df00f1032289718a3ad8b2d131de |
sfc-gh-swinkler
approved these changes
Oct 13, 2023
sfc-gh-jcieslak
approved these changes
Oct 13, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
After moving integration tests to a separate package in #2111 and #2115, it is possible now to reuse a common setup. This PR is about setting up a database only once for all integration tests and cleaning it up at the end.
Changes