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: Spring assumes the responsibility for resolving _all_ parameters in the constructor.
  Consequently, no other `ParameterResolver` registered with JUnit Jupiter can resolve
  parameters for such a constructor.
  
  In the following example, Spring injects the `OrderService` bean from the
  `ApplicationContext` loaded from `TestConfig.class` into the
  
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.
  
  