anchor.diff:  ==== Testing request and session scoped beans
   
   <<beans-factory-scopes-other,Request and session scoped beans>> have been supported by
  -Spring for several years now, but it's always been a bit non-trivial to test them. As of
  -Spring 3.2 it's a breeze to test your request-scoped and session-scoped beans by
  -following these steps.
  +Spring since the early years, and since Spring 3.2 it's a breeze to test your
  +request-scoped and session-scoped beans by following these steps.
   
   * Ensure that a `WebApplicationContext` is loaded for your test by annotating your test
     class with `@WebAppConfiguration`.
  
positive.code: 
  [[integration-testing-annotations-meta]]
  ==== Meta-Annotation Support for Testing
  As of Spring Framework 4.0, it is possible to use test-related annotations as
  <<beans-meta-annotations,meta-annotations>> in order to create custom _composed annotations_
  and reduce configuration duplication across a test suite.
  
  
negative.code: have a parent context that provides configuration for shared batch infrastructure and a
  child context for the configuration of a specific batch job.
  
  Since Spring Framework 3.2.2, it is possible to write integration tests that use context
  hierarchies by declaring context configuration via the `@ContextHierarchy` annotation,
  either on an individual test class or within a test class hierarchy. If a context
  hierarchy is declared on multiple classes within a test class hierarchy it is also
  