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: 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 <<integration-testing-annotations-spring>>). This instructs Spring
  to remove the context from the cache and rebuild the application context before running
  the next test. Note that support for the `@DirtiesContext` annotation is provided by the
  `DirtiesContextBeforeModesTestExecutionListener` and the
  `DirtiesContextTestExecutionListener`, which are enabled by default.
  
  
negative.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.
  
  [WARNING]
  ====
  Constructor injection for test classes must not be used in conjunction with JUnit
  Jupiter's `@TestInstance(PER_CLASS)` support if `@DirtiesContext` is used to close the
  test's `ApplicationContext` before or after test methods.
  
  The reason is that `@TestInstance(PER_CLASS)` instructs JUnit Jupiter to cache the test
  instance between test method invocations. Consequently, the test instance will retain
  references to beans that were originally injected from an `ApplicationContext` that has
  been subsequently closed. Since the constructor for the test class will only be invoked
  once in such scenarios, dependency injection will not occur again, and subsequent tests
  will interact with beans from the closed `ApplicationContext` which may result in errors.
  
  To use `@DirtiesContext` with "before test method" or "after test method" modes in
  conjunction with `@TestInstance(PER_CLASS)`, one must configure dependencies from Spring
  to be supplied via field or setter injection so that they can be re-injected between test
  method invocations.
  ====
  
  In the following example, Spring injects the `OrderService` bean from the
  `ApplicationContext` loaded from `TestConfig.class` into the
  