Polish contribution

See gh-31723
This commit is contained in:
Sam Brannen 2023-12-04 15:09:33 +01:00
parent 87d37a21aa
commit 8ed04b5dd1
2 changed files with 12 additions and 11 deletions

View File

@ -42,13 +42,15 @@ become cumbersome if a custom factory needs to be used across an entire test sui
issue is addressed through support for automatic discovery of default issue is addressed through support for automatic discovery of default
`ContextCustomizerFactory` implementations through the `SpringFactoriesLoader` mechanism. `ContextCustomizerFactory` implementations through the `SpringFactoriesLoader` mechanism.
Specifically, the modules that make up the testing support in Spring Framework and Spring For example, the modules that make up the testing support in Spring Framework and Spring
Boot declare all core default `ContextCustomizerFactory` implementations under the Boot declare all core default `ContextCustomizerFactory` implementations under the
`org.springframework.test.context.ContextCustomizerFactory` key in their `org.springframework.test.context.ContextCustomizerFactory` key in their
{spring-framework-code}/spring-test/src/main/resources/META-INF/spring.factories[`META-INF/spring.factories`] `META-INF/spring.factories` properties files. The `spring.factories` file for the
properties files. Third-party frameworks and developers can contribute their own `spring-test` module can be viewed
`ContextCustomizerFactory` implementations to the list of default factories in the same {spring-framework-code}/spring-test/src/main/resources/META-INF/spring.factories[here].
manner through their own `META-INF/spring.factories` properties files. Third-party frameworks and developers can contribute their own `ContextCustomizerFactory`
implementations to the list of default factories in the same manner through their own
`spring.factories` files.
[[testcontext-context-customizers-merging]] [[testcontext-context-customizers-merging]]

View File

@ -80,13 +80,12 @@ become cumbersome if a custom listener needs to be used across an entire test su
issue is addressed through support for automatic discovery of default issue is addressed through support for automatic discovery of default
`TestExecutionListener` implementations through the `SpringFactoriesLoader` mechanism. `TestExecutionListener` implementations through the `SpringFactoriesLoader` mechanism.
Specifically, the `spring-test` module declares all core default `TestExecutionListener` For example, the `spring-test` module declares all core default `TestExecutionListener`
implementations under the `org.springframework.test.context.TestExecutionListener` key in implementations under the `org.springframework.test.context.TestExecutionListener` key in
{spring-framework-code}/spring-test/src/main/resources/META-INF/spring.factories[its its {spring-framework-code}/spring-test/src/main/resources/META-INF/spring.factories[`META-INF/spring.factories`
`META-INF/spring.factories` properties file]. Third-party frameworks and developers can properties file]. Third-party frameworks and developers can contribute their own
contribute their own `TestExecutionListener` implementations to the list of default `TestExecutionListener` implementations to the list of default listeners in the same
listeners in the same manner through their own `META-INF/spring.factories` properties manner through their own `spring.factories` files.
file.
[[testcontext-tel-config-ordering]] [[testcontext-tel-config-ordering]]
== Ordering `TestExecutionListener` Implementations == Ordering `TestExecutionListener` Implementations