anchor.diff:  configuration.
   
   In addition to generic testing infrastructure, the TestContext framework provides
  -explicit support for JUnit 4 and TestNG in the form of `abstract` support classes. For
  -JUnit 4, Spring also provides a custom JUnit `Runner` and custom JUnit `Rules` that allow
  -one to write so-called __POJO test classes__. POJO test classes are not required to
  -extend a particular class hierarchy.
  -
  -The following section provides an overview of the internals of the TestContext
  -framework. If you are only interested in _using_ the framework and not necessarily
  -interested in _extending_ it with your own custom listeners or custom loaders, feel free
  -to go directly to the configuration (<<testcontext-ctx-management,context management>>,
  +explicit support for JUnit 4, JUnit Jupiter (a.k.a., JUnit 5), and TestNG. For JUnit 4
  +and TestNG, Spring provides `abstract` support classes. Furthermore, Spring provides a
  +custom JUnit `Runner` and custom JUnit `Rules` for _JUnit 4_ as well as a custom
  +`Extension` for _JUnit Jupiter_ that allow one to write so-called __POJO test classes__.
  +POJO test classes are not required to extend a particular class hierarchy such as the
  +`abstract` support classes.
  +
  +The following section provides an overview of the internals of the TestContext framework.
  +If you are only interested in _using_ the framework and not necessarily interested in
  +_extending_ it with your own custom listeners or custom loaders, feel free to go directly
  +to the configuration (<<testcontext-ctx-management,context management>>,
   <<testcontext-fixture-di,dependency injection>>, <<testcontext-tx,transaction
   management>>), <<testcontext-support-classes,support classes>>, and
   <<integration-testing-annotations,annotation support>> sections.
  
positive.code: 
  [TIP]
  ====
  Any __before methods__ (such as methods annotated with JUnit 4's `@Before`) and any __after
  methods__ (such as methods annotated with JUnit 4's `@After`) are executed __within__ a
  transaction. In addition, methods annotated with `@BeforeTransaction` or
  `@AfterTransaction` are naturally not executed for test methods that are not configured
  to run within a transaction.
  ====
  
  [[testcontext-tx-mgr-config]]
  
negative.code: [[testcontext-tx-annotation-demo]]
  ===== Demonstration of all transaction-related annotations
  
  The following JUnit 4 based example displays a _fictitious_ integration testing scenario
  highlighting all transaction-related annotations. The example is **not** intended to
  demonstrate best practices but rather to demonstrate how these annotations can be used.
  Consult the <<integration-testing-annotations,annotation support>> section for further
  