anchor.diff:  
   [TIP]
   ====
  -Any __before methods__ (such as methods annotated with JUnit's `@Before`) and any __after
  -methods__ (such as methods annotated with JUnit's `@After`) are executed __within__ a
  +Any __before methods__ (such as methods annotated with JUnit 4's `@Before`) and any __after
  +methods__ (such as methods annotated with JUnit 4's `@After`) are executed __within__ a
   transaction. In addition, methods annotated with `@BeforeTransaction` or
   `@AfterTransaction` are naturally not executed for test methods that are not configured
   to run within a transaction.
  
positive.code: configuration.
  
  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` 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.
  
  
negative.code: [NOTE]
  ====
  The dependency injection behavior in the following code listings is not specific to
  JUnit 4. The same DI techniques can be used in conjunction with any testing framework.
  
  The following examples make calls to static assertion methods such as `assertNotNull()`
  but without prepending the call with `Assert`. In such cases, assume that the method was
  