anchor.diff:  `@ContextConfiguration` declares the application context resource `locations` or the
   annotated `classes` used to load the context.
   
  -Resource locations are typically XML configuration files or Groovy scripts located in
  -the classpath, while annotated classes are typically `@Configuration` classes. However,
  +Resource locations are typically XML configuration files or Groovy scripts located in the
  +classpath, while annotated classes are typically `@Configuration` classes. However,
   resource locations can also refer to files and scripts in the file system, and annotated
   classes can be component classes, and so on.
   
  
positive.code: 
  If application code relies on Servlet request parameters and does not check the query
  string explicitly (as is most often the case), it does not matter which option you use.
  Keep in mind, however, that query paramaters provided with the URI template are decoded while
  request parameters provided through the `param(...)` method are expected to already be decoded.
  
  In most cases, it is preferable to leave the context path and the Servlet path out of
  the request URI. If you must test with the full request URI, be sure to set the
  `contextPath` and `servletPath` accordingly so that request mappings work, as the following example shows:
  
  ====
  [source,java,indent=0]
  
negative.code: [[spring-mvc-test-client]]
  ==== Client-Side REST Tests
  
  You can use client-side tests to test code that internally uses the `RestTemplate`. The
  idea is to declare expected requests and to provide "`stub`" responses so that you can
  focus on testing the code in isolation (that is, without running a server). The following
  example shows how to do so:
  
  ====
  [source,java,indent=0]
  