anchor.diff:  ----
   ====
   
  -Since you can also use annotations in JUnit 5 as meta-annotations, Spring can provide the
  +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.
   
  
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: In the unlikely case that a test corrupts the application context and requires reloading
  (for example, by modifying a bean definition or the state of an application object), you
  can annotate your test class or test method with `@DirtiesContext` (see the discussion of
  `@DirtiesContext` in <<spring-testing-annotation-dirtiescontext>>). This instructs Spring
  to remove the context from the cache and rebuild the application context before running
  the next test that requires the same application context. Note that support for the
  `@DirtiesContext` annotation is provided by the
  `DirtiesContextBeforeModesTestExecutionListener` and the
  `DirtiesContextTestExecutionListener`, which are enabled by default.
  
  