anchor.diff:  ----
   ====
   
  -NOTE: This is a simple example of using `MockMvcHtmlUnitDriverBuilder`.
  -For more advanced usage, see <<spring-mvc-test-server-htmlunit-webdriver-advanced-builder>>.
  -
  -This ensures that any URL referencing `localhost` as the server is directed to
  -our `MockMvc` instance without the need for a real HTTP connection. Any other URL is
  +NOTE: This is a simple example of using `MockMvcHtmlUnitDriverBuilder`. For more advanced
  +usage, see <<spring-mvc-test-server-htmlunit-webdriver-advanced-builder>>.
  +
  +This ensures that any URL referencing `localhost` as the server is directed to our
  +`MockMvc` instance without the need for a real HTTP connection. Any other URL is
   requested by using a network connection as normal. This lets us easily test the use of
   CDNs.
   
  
positive.code: [[testcontext-framework]]
  === Spring TestContext Framework
  
  The Spring TestContext Framework (located in the
  `org.springframework.test.context` package) provides generic, annotation-driven unit and
  integration testing support that is agnostic of the testing framework in use. The
  TestContext framework also places a great deal of importance on convention over
  configuration, with reasonable defaults that you can override through annotation-based
  configuration.
  
  In addition to generic testing infrastructure, the TestContext framework provides
  explicit support for JUnit 4, JUnit Jupiter (AKA JUnit 5), and TestNG. For JUnit 4
  and TestNG, Spring provides `abstract` support classes. Furthermore, Spring provides a
  custom JUnit `Runner` and custom JUnit `Rules` for JUnit 4 and a custom
  `Extension` for JUnit Jupiter that let you write so-called POJO test classes.
  POJO test classes are not required to extend a particular class hierarchy, such as the
  `abstract` support classes.
  
  The following section provides an overview of the internals of the TestContext framework.
  If you are interested only in using the framework and are not interested in
  extending it with your own custom listeners or custom loaders, feel free to go directly
  to the configuration (<<testcontext-ctx-management,context management>>,
  <<testcontext-fixture-di,dependency injection>>, <<testcontext-tx,transaction
  management>>), <<testcontext-support-classes,support classes>>, and
  <<integration-testing-annotations,annotation support>> sections.
  
negative.code: `ApplicationContext` was removed from the `ContextCache` in a different thread.
  
  This may be due to the use of `@DirtiesContext` or due to automatic eviction from the
  `ContextCache`. If `@DirtiesContext` is the culprit, you either need to find a way to
  avoid using `@DirtiesContext` or exclude such tests from parallel execution. If the
  maximum size of the `ContextCache` has been exceeded, you can increase the maximum size
  of the cache. See the discussion on <<testcontext-ctx-management-caching,context
  caching>> for details.
  ====
  
  WARNING: Parallel test execution in the Spring TestContext Framework is only possible if
  the underlying `TestContext` implementation provides a copy constructor, as explained in
  the {api-spring-framework}/test/context/TestContext.html[Javadoc for `TestContext`]. The
  `DefaultTestContext` used in Spring provides such a constructor. However, if you use a
  third-party library that provides a custom `TestContext` implementation, you need to
  verify that it is suitable for parallel test execution.
  
  
  
  