Improve deployment integration tests #25446
Closed
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.
Hi,
this PR improves the
spring-boot-deployment-tests
build step by splitting them apart based on their underlying container (e.g. Wildfly, TomEE etc.).By doing so we can make use of static per-class testcontainers instead of starting a container for every test. This reduces the amount of started containers from 12 to 4 and therefore obviously the test time as well. (On my machine it only takes a third of what it took before). My hope is that this reduces the pressure on CI as well and helps to minimize flaky tests reported in #25410.
Let me know what you think.
Cheers,
Christoph
P.S.: The separate renaming commit was kind of intentional in order to preserve history for
DeploymentIntegrationTests
.