anchor.diff:  NOTE: If you use `@DirtiesContext` in a test whose context is configured as part of a
   context hierarchy, you can use the `hierarchyMode` flag to control how the context cache
   is cleared. For further details, see the discussion of `@DirtiesContext` in
  -<<integration-testing-annotations-spring,Spring Testing Annotations>> and the
  +<<spring-testing-annotation-dirtiescontext,Spring Testing Annotations>> and the
   {api-spring-framework}/test/annotation/DirtiesContext.html[`@DirtiesContext`] javadoc.
   --
  -
   
   [[testcontext-fixture-di]]
   ==== Dependency Injection of Test Fixtures
  
positive.code: such as support for loading application contexts, dependency injection of test instances,
  transactional test method execution, and so on.
  
  Furthermore, thanks to the rich extension API in JUnit Jupiter, Spring can provide the
  following features above and beyond the feature set that Spring supports for JUnit 4 and
  TestNG:
  
  
negative.code: ----
  ====
  
  Since you can also use annotations in JUnit 5 as meta-annotations, Spring provides the
  `@SpringJUnitConfig` and `@SpringJUnitWebConfig` composed annotations to simplify the
  configuration of the test `ApplicationContext` and JUnit Jupiter.
  
  