Honor @NestedTestConfiguration
semantic in BatchTestContextCustomizerFactory
#4739
+92
−11
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.
Prior to this commit,
BatchTestContextCustomizerFactory
only looked for@SpringBatchTest
on the given test class as a marker annotation. While this works fine for top-level classes, it doesn't work correctly with JUnit@Nested
classes, resulting in a distinctApplicationContext
for the nested class as a side effect.With this change, the factory no longer uses
AnnotatedElementUtils.hasAnnotation
and favors insteadTestContextAnnotationUtils.hasAnnotation
, which honors the@NestedTestConfiguration
semantic.Fixes #4738.