OPIK-669: Make containers start when test instance is init #1412
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
thiagohora
force-pushed
the
thiagohora/OPIK-669_make_containers_start_when_test_instance_is_instanciated
branch
from
a050be4 to
b44473b
Compare
…en_test_instance_is_instanciated
…en_test_instance_is_instanciated
thiagohora
deleted the
thiagohora/OPIK-669_make_containers_start_when_test_instance_is_instanciated
branch
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.
Details
In this PR, we introduce a new Junit5 extension that allows us to postpone the application context setup to the before-all method. This makes the container instance-based instead of static-based, making container initialization lazy instead of eager.
Testing
Tested via CI