Register EventPublishingTestExecutionListener by default
Closes gh-18490
This commit is contained in:
parent
d6173512fe
commit
13543f5e0f
|
|
@ -61,14 +61,6 @@ import org.springframework.test.context.support.AbstractTestExecutionListener;
|
|||
* support. For further details, consult the class-level Javadoc for
|
||||
* {@link org.springframework.context.event.EventListener @EventListener}.
|
||||
*
|
||||
* <h3>Listener Registration</h3>
|
||||
* <p>Note that this {@code TestExecutionListener} is not registered by default,
|
||||
* but it may be registered for a given test class via
|
||||
* {@link org.springframework.test.context.TestExecutionListeners @TestExecutionListeners}
|
||||
* or globally via the {@link org.springframework.core.io.support.SpringFactoriesLoader
|
||||
* SpringFactoriesLoader} mechanism (consult the Javadoc and Spring reference manual for
|
||||
* details).
|
||||
*
|
||||
* @author Frank Scheffler
|
||||
* @author Sam Brannen
|
||||
* @since 5.2
|
||||
|
|
|
|||
|
|
@ -1,6 +1,7 @@
|
|||
# Default TestExecutionListeners for the Spring TestContext Framework
|
||||
#
|
||||
org.springframework.test.context.TestExecutionListener = \
|
||||
org.springframework.test.context.event.EventPublishingTestExecutionListener,\
|
||||
org.springframework.test.context.web.ServletTestExecutionListener,\
|
||||
org.springframework.test.context.support.DirtiesContextBeforeModesTestExecutionListener,\
|
||||
org.springframework.test.context.support.DependencyInjectionTestExecutionListener,\
|
||||
|
|
|
|||
|
|
@ -41,7 +41,6 @@ import org.springframework.test.context.ContextConfiguration;
|
|||
import org.springframework.test.context.TestContext;
|
||||
import org.springframework.test.context.TestContextManager;
|
||||
import org.springframework.test.context.TestExecutionListener;
|
||||
import org.springframework.test.context.TestExecutionListeners;
|
||||
import org.springframework.test.context.event.annotation.AfterTestClass;
|
||||
import org.springframework.test.context.event.annotation.AfterTestExecution;
|
||||
import org.springframework.test.context.event.annotation.AfterTestMethod;
|
||||
|
|
@ -193,7 +192,6 @@ public class EventPublishingTestExecutionListenerIntegrationTests {
|
|||
|
||||
@RunWith(SpringRunner.class)
|
||||
@ContextConfiguration(classes = TestEventListenerConfiguration.class)
|
||||
@TestExecutionListeners(EventPublishingTestExecutionListener.class)
|
||||
public static class ExampleTestCase {
|
||||
|
||||
@Traceable
|
||||
|
|
|
|||
|
|
@ -1659,8 +1659,7 @@ subclasses instead.
|
|||
==== `TestExecutionListener` Configuration
|
||||
|
||||
Spring provides the following `TestExecutionListener` implementations that are registered
|
||||
exactly in the following order. Except for the `EventPublishingTestExecutionListener`,
|
||||
each of these listeners is registered by default.
|
||||
by default, exactly in the following order:
|
||||
|
||||
* `EventPublishingTestExecutionListener`: Publishes test execution events to the test's
|
||||
`ApplicationContext` (see <<testcontext-test-execution-events>>).
|
||||
|
|
@ -1786,11 +1785,10 @@ be replaced with the following:
|
|||
==== Test Execution Events
|
||||
|
||||
The `EventPublishingTestExecutionListener` introduced in Spring Framework 5.2 offers an
|
||||
alternative approach to implementing a custom `TestExecutionListener`. If the
|
||||
`EventPublishingTestExecutionListener` is <<testcontext-tel-config-registering-tels,
|
||||
registered>>, components in the `ApplicationContext` can listen to the following events
|
||||
published by the `EventPublishingTestExecutionListener`. Each of these events corresponds
|
||||
to a method in the `TestExecutionListener` API.
|
||||
alternative approach to implementing a custom `TestExecutionListener`. Components in the
|
||||
test `ApplicationContext` can listen to the following events published by the
|
||||
`EventPublishingTestExecutionListener`, each of which corresponds to a method in the
|
||||
`TestExecutionListener` API.
|
||||
|
||||
* `BeforeTestClassEvent`
|
||||
* `PrepareTestInstanceEvent`
|
||||
|
|
|
|||
Loading…
Reference in New Issue