Document wrapping behavior for TestExecutionListener callbacks

Closes gh-34422

Author: sbrannen

spring-test/src/main/java/org/springframework/test/context/TestExecutionListener.java

@@ -42,6 +42,35 @@
  * {@link org.springframework.core.annotation.Order @Order} annotation. See
  * {@link TestContextBootstrapper#getTestExecutionListeners()} for details.
  *
+ * <h3>Wrapping Behavior for Listeners</h3>
+ *
+ * <p>The {@link TestContextManager} guarantees <em>wrapping</em> behavior for
+ * multiple registered listeners that implement lifecycle callbacks such as
+ * {@link #beforeTestClass(TestContext) beforeTestClass},
+ * {@link #afterTestClass(TestContext) afterTestClass},
+ * {@link #beforeTestMethod(TestContext) beforeTestMethod},
+ * {@link #afterTestMethod(TestContext) afterTestMethod},
+ * {@link #beforeTestExecution(TestContext) beforeTestExecution}, and
+ * {@link #afterTestExecution(TestContext) afterTestExecution}. This means that,
+ * given two listeners {@code Listener1} and {@code Listener2} with {@code Listener1}
+ * registered before {@code Listener2}, any <em>before</em> callbacks implemented
+ * by {@code Listener1} are guaranteed to be invoked <strong>before</strong> any
+ * <em>before</em> callbacks implemented by {@code Listener2}. Similarly, given
+ * the same two listeners registered in the same order, any <em>after</em>
+ * callbacks implemented by {@code Listener1} are guaranteed to be invoked
+ * <strong>after</strong> any <em>after</em> callbacks implemented by
+ * {@code Listener2}. {@code Listener1} is therefore said to <em>wrap</em>
+ * {@code Listener2}.
+ *
+ * <p>For a concrete example, consider the relationship between the
+ * {@link org.springframework.test.context.transaction.TransactionalTestExecutionListener
+ * TransactionalTestExecutionListener} and the
+ * {@link org.springframework.test.context.jdbc.SqlScriptsTestExecutionListener
+ * SqlScriptsTestExecutionListener}. The {@code SqlScriptsTestExecutionListener}
+ * is registered after the {@code TransactionalTestExecutionListener}, so that
+ * SQL scripts are executed within a transaction managed by the
+ * {@code TransactionalTestExecutionListener}.
+ *
  * <h3>Registering TestExecutionListener Implementations</h3>
  *
  * <p>A {@code TestExecutionListener} can be registered explicitly for a test class,
@@ -101,6 +130,8 @@ public interface TestExecutionListener {
 	 * the class.
 	 * <p>This method should be called immediately before framework-specific
 	 * <em>before class</em> lifecycle callbacks.
+	 * <p>See the {@linkplain TestExecutionListener class-level documentation}
+	 * for details on wrapping behavior for lifecycle callbacks.
 	 * <p>The default implementation is <em>empty</em>. Can be overridden by
 	 * concrete classes as necessary.
 	 * @param testContext the test context for the test; never {@code null}
@@ -119,6 +150,8 @@ default void beforeTestClass(TestContext testContext) throws Exception {
 	 * {@link org.springframework.test.context.junit4.rules.SpringMethodRule
 	 * SpringMethodRule}). In any case, this method must be called prior to any
 	 * framework-specific lifecycle callbacks.
+	 * <p>See the {@linkplain TestExecutionListener class-level documentation}
+	 * for details on wrapping behavior for listeners.
 	 * <p>The default implementation is <em>empty</em>. Can be overridden by
 	 * concrete classes as necessary.
 	 * @param testContext the test context for the test; never {@code null}
@@ -138,6 +171,8 @@ default void prepareTestInstance(TestContext testContext) throws Exception {
 	 * this method might be something like {@code beforeTestSetUp} or
 	 * {@code beforeEach}; however, it is unfortunately impossible to rename
 	 * this method due to backward compatibility concerns.
+	 * <p>See the {@linkplain TestExecutionListener class-level documentation}
+	 * for details on wrapping behavior for lifecycle callbacks.
 	 * <p>The default implementation is <em>empty</em>. Can be overridden by
 	 * concrete classes as necessary.
 	 * @param testContext the test context in which the test method will be
@@ -157,6 +192,8 @@ default void beforeTestMethod(TestContext testContext) throws Exception {
 	 * or logging purposes.
 	 * <p>This method <strong>must</strong> be called after framework-specific
 	 * <em>before</em> lifecycle callbacks.
+	 * <p>See the {@linkplain TestExecutionListener class-level documentation}
+	 * for details on wrapping behavior for lifecycle callbacks.
 	 * <p>The default implementation is <em>empty</em>. Can be overridden by
 	 * concrete classes as necessary.
 	 * @param testContext the test context in which the test method will be
@@ -177,6 +214,8 @@ default void beforeTestExecution(TestContext testContext) throws Exception {
 	 * or logging purposes.
 	 * <p>This method <strong>must</strong> be called before framework-specific
 	 * <em>after</em> lifecycle callbacks.
+	 * <p>See the {@linkplain TestExecutionListener class-level documentation}
+	 * for details on wrapping behavior for lifecycle callbacks.
 	 * <p>The default implementation is <em>empty</em>. Can be overridden by
 	 * concrete classes as necessary.
 	 * @param testContext the test context in which the test method will be
@@ -201,6 +240,8 @@ default void afterTestExecution(TestContext testContext) throws Exception {
 	 * this method might be something like {@code afterTestTearDown} or
 	 * {@code afterEach}; however, it is unfortunately impossible to rename
 	 * this method due to backward compatibility concerns.
+	 * <p>See the {@linkplain TestExecutionListener class-level documentation}
+	 * for details on wrapping behavior for lifecycle callbacks.
 	 * <p>The default implementation is <em>empty</em>. Can be overridden by
 	 * concrete classes as necessary.
 	 * @param testContext the test context in which the test method was
@@ -218,6 +259,8 @@ default void afterTestMethod(TestContext testContext) throws Exception {
 	 * the class.
 	 * <p>This method should be called immediately after framework-specific
 	 * <em>after class</em> lifecycle callbacks.
+	 * <p>See the {@linkplain TestExecutionListener class-level documentation}
+	 * for details on wrapping behavior for lifecycle callbacks.
 	 * <p>The default implementation is <em>empty</em>. Can be overridden by
 	 * concrete classes as necessary.
 	 * @param testContext the test context for the test; never {@code null}