anchor.diff:  
   In addition to generic testing infrastructure, the TestContext framework provides
   explicit support for JUnit and TestNG in the form of `abstract` support classes. For
  -JUnit, Spring also provides a custom JUnit `Runner` that allows one to write so-called
  -__POJO test classes__. POJO test classes are not required to extend a particular class
  -hierarchy.
  +JUnit, Spring also provides a custom JUnit `Runner` and custom JUnit `Rules` that allow
  +one to write so-called __POJO test classes__. POJO test classes are not required to
  +extend a particular class hierarchy.
   
   The following section provides an overview of the internals of the TestContext
   framework. If you are only interested in using the framework and not necessarily
  
positive.code: 		.build()
  ----
  
  Note that the expectation is __always__ applied and cannot be overridden without
  creating a separate `MockMvc` instance.
  
  When JSON response content contains hypermedia links created with
  https://github.com/spring-projects/spring-hateoas[Spring HATEOAS], the resulting links can
  be verified:
  
  [source,java,indent=0]
  [subs="verbatim,quotes"]
  
negative.code: 
  As long as request processing does not cause an unhandled exception, the `print()` method
  will print all the available result data to `System.out`. Spring Framework 4.2 introduces
  a `log()` method and two additional variants of the `print()` method, one that accepts
  an `OutputStream` and one that accepts a `Writer`. For example, invoking
  `print(System.err)` will print the result data to `System.err`; while invoking
  `print(myWriter)` will print the result data to a custom writer. If you would like to
  