Allow to warm up Docker services before E2E tests - #6
Merged
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 adds optional PHPUnit-driven Docker service warm-up for E2E test suites.
Without the extension, Docker services continue to start on demand. When configured for selected test suites, the extension discovers the services advertised by their test classes and starts them before the tests run. It does not wait for database readiness during warm-up, allowing e.g. multiple database variants to start early while other test setup continues.
The managed-edition base test case automatically exposes the Docker services required by its configuration. Tests with another base class can implement
DockerServiceProviderInterfacedirectly. The generic service interface also leaves room for services other than databases.