Retain application context between test classes #36069
Closed
+43
−5
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.
Problem:
Tests using @SpringBootTest are slower in Spring Boot 4.0 because
ApplicationContext is paused/restarted between test classes even
when they share the same context. This particularly affects tests
with expensive SmartLifecycle beans like Kafka consumers.
Solution:
Introduce @RetainApplicationContext annotation to mark test classes
whose context should not be paused/restarted. Update
DefaultTestContext.markApplicationContextUnused() to check for this
annotation before unregistering context usage.
Usage:
Annotate abstract test classes with @RetainApplicationContext to
retain context between subclasses, reducing overhead.
Closes gh-36044