anchor.diff:  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
  +Furthermore, thanks to the rich extension API in JUnit Jupiter, Spring provides the
   following features above and beyond the feature set that Spring supports for JUnit 4 and
   TestNG:
   
  
positive.code: 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
  {api-spring-framework}/test/annotation/DirtiesContext.html[`@DirtiesContext`] javadoc.
  --
  
  
  [[testcontext-fixture-di]]
  ==== Dependency Injection of Test Fixtures
  
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.
  
  