Overview
Although #35680 introduced support for JUnit Jupiter's TEST_METHOD ExtensionContextScope in the SpringExtension and BeanOverrideTestExecutionListener, those were internal changes that are not directly visible by TestExecutionListener authors.
However, in order to be compatible with a test-method scoped TestContext (which takes its values from the current Jupiter ExtensionContext), existing third-party TestExecutionListener implementations may need to be modified similar to how BeanOverrideTestExecutionListener was modified in commit d24a31d.
To raise awareness, we should document test-method TestContext semantics for TestExecutionListener authors in Spring Framework 6.2.x.
Related Issues
Overview
Although #35680 introduced support for JUnit Jupiter's
TEST_METHODExtensionContextScopein theSpringExtensionandBeanOverrideTestExecutionListener, those were internal changes that are not directly visible byTestExecutionListenerauthors.However, in order to be compatible with a test-method scoped
TestContext(which takes its values from the current JupiterExtensionContext), existing third-partyTestExecutionListenerimplementations may need to be modified similar to howBeanOverrideTestExecutionListenerwas modified in commit d24a31d.To raise awareness, we should document test-method
TestContextsemantics forTestExecutionListenerauthors in Spring Framework 6.2.x.Related Issues
TEST_METHODExtensionContextScopeis not fully supported #35680ExtensionContextin theSpringExtension#35697