anchor.diff:  * `locations` __(from @ContextConfiguration)__
   * `classes` __(from @ContextConfiguration)__
   * `contextInitializerClasses` __(from @ContextConfiguration)__
  +* `contextCustomizers` __(from ContextCustomizerFactory)__
   * `contextLoader` __(from @ContextConfiguration)__
   * `parent` __(from @ContextHierarchy)__
   * `activeProfiles` __(from @ActiveProfiles)__
  
positive.code: ==== 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.
  
  * Ensure that a `WebApplicationContext` is loaded for your test by annotating your test
    class with `@WebAppConfiguration`.
  
negative.code: 
  Registering custom ++TestExecutionListener++s via `@TestExecutionListeners` is suitable
  for custom listeners that are used in limited testing scenarios; however, it can become
  cumbersome if a custom listener needs to be used across a test suite. Since Spring
  Framework 4.1, this issue is addressed via support for automatic discovery of _default_
  `TestExecutionListener` implementations via the `SpringFactoriesLoader` mechanism.
  
  Specifically, the `spring-test` module declares all core default
  