spring-framework

Spring Framework

Sam Brannen 69e4cc5576 Ensure context caching works properly during AOT runtime in the TCF Prior to this commit, the AOT runtime support in the Spring TestContext Framework (TCF) relied on the MergedContextConfiguration for a given test class being the same as during the AOT processing phase. However, this is not always the case. For example, Spring Boot "disables" selected `ContextCustomizer` implementations during AOT runtime execution. See `0f325f98b5` To address that, this commit ensures that context caching works properly during AOT runtime execution even if the MergedContextConfiguration differs from what was produced during the AOT processing phase. Specifically, this commit introduces AotMergedContextConfiguration which is a MergedContextConfiguration implementation based on an AOT-generated ApplicationContextInitializer. AotMergedContextConfiguration wraps the MergedContextConfiguration built during AOT runtime execution. Interactions with the ContextCache are performed using the AotMergedContextConfiguration; whereas, the ApplicationContext is loaded using the original MergedContextConfiguration. This commit also introduces a ContextCustomizerFactory that emulates the ImportsContextCustomizerFactory in Spring Boot's testing support. BasicSpringJupiterImportedConfigTests uses @Import to verify that the context customizer works, and AotIntegrationTests has been updated to execute BasicSpringJupiterImportedConfigTests after test classes whose MergedContextConfiguration is identical during AOT runtime execution. Without the fix in this commit, BasicSpringJupiterImportedConfigTests would fail in AOT runtime mode since its ApplicationContext would be pulled from the cache using an inappropriate cache key. Closes gh-29289		4 years ago
..
src	Ensure context caching works properly during AOT runtime in the TCF	4 years ago
.springBeans	…
spring-test.gradle	Support context propagation for Spring MVC controllers	4 years ago