anchor.diff:  
   +
   
  -Spring's `@Timed` annotation has different semantics than JUnit's `@Test(timeout=...)`
  -support. Specifically, due to the manner in which JUnit handles test execution timeouts
  +Spring's `@Timed` annotation has different semantics than JUnit 4's `@Test(timeout=...)`
  +support. Specifically, due to the manner in which JUnit 4 handles test execution timeouts
   (that is, by executing the test method in a separate `Thread`), `@Test(timeout=...)`
   preemptively fails the test if the test takes too long. Spring's `@Timed`, on the other
   hand, does not preemptively fail the test but rather waits for the test to complete
  
positive.code: consistent; otherwise, it is perfectly acceptable to have different levels in a context
  hierarchy configured using different resource types.
  
  The following JUnit-based examples demonstrate common configuration scenarios for
  integration tests that require the use of context hierarchies.
  
  .Single test class with context 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
  