anchor.diff:  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
  -interested in extending it with your own custom listeners or custom loaders, feel free
  +framework. If you are only interested in _using_ the framework and not necessarily
  +interested in _extending_ it with your own custom listeners or custom loaders, feel free
   to go directly to the configuration (<<testcontext-ctx-management,context management>>,
   <<testcontext-fixture-di,dependency injection>>, <<testcontext-tx,transaction
   management>>), <<testcontext-support-classes,support classes>>, and
  
positive.code: methods within a single test class in JUnit 4). The `TestContextManager` in turn manages a
  `TestContext` that holds the context of the current test. The `TestContextManager` also
  updates the state of the `TestContext` as the test progresses and delegates to
  ++TestExecutionListener++s, which instrument the actual test execution by providing
  dependency injection, managing transactions, and so on. A `SmartContextLoader` is
  responsible for loading an `ApplicationContext` for a given test class. Consult the
  javadocs and the Spring test suite for further information and examples of various
  implementations.
  
  
negative.code: 
  Implement `SmartContextLoader` instead of this interface in order to provide support for
  annotated classes, active bean definition profiles, test property sources, context
  hierarchies, and `WebApplicationContext` support.
  
  * `SmartContextLoader`: Extension of the `ContextLoader` interface introduced in Spring
    3.1.
  