anchor.diff:  available in the `spring-test` module. This allows performing requests and generating
   responses without the need for running in a Servlet container. For the most part
   everything should work as it does at runtime with a few notable exceptions as
  -explained further below. Here is an example of using Spring MVC Test:
  +explained in <<spring-mvc-test-vs-end-to-end-integration-tests>>.
  +Here is an example of using Spring MVC Test:
   
   [source,java,indent=0]
   ----
  
positive.code: 
  Registered filters will be invoked through `MockFilterChain` from `spring-test` and the
  last filter will delegates to the `DispatcherServlet`.
  
  [[spring-mvc-test-server-resources]]
  ===== Further Server-Side Test Examples
  
negative.code: the `RestTemplate`. Client-side tests mock the server responses and also do not
  require a running server.
  
  [TIP]
  ====
  Spring Boot provides an option to write full, end-to-end integration tests that include
  a running server. If this is your goal please have a look at the
  http://docs.spring.io/spring-boot/docs/current/reference/html/boot-features-testing.html#boot-features-testing-spring-boot-applications[Spring Boot reference page].
  For more on the difference with end-to-end integration tests see
  <<spring-mvc-test-vs-end-to-end-integration-tests>>.
  ====
  
  
  
  [[spring-mvc-test-server]]
  