anchor.diff:  will be loaded using the specified resource protocol.
   
   The following example demonstrates how to use `@Sql` at the class level and at the method
  -level within a JUnit-based integration test class.
  +level within a JUnit 4 based integration test class.
   
   [source,java,indent=0]
   [subs="verbatim,quotes"]
  
positive.code: [NOTE]
  ====
  The dependency injection behavior in the following code listings is not specific to
  JUnit. 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
  
negative.code: 
  In contrast to the `SpringRunner`, Spring's rule-based JUnit support has the advantage
  that it is independent of any `org.junit.runner.Runner` implementation and can therefore
  be combined with existing alternative runners like JUnit 4's `Parameterized` or third-party
  runners such as the `MockitoJUnitRunner`.
  
  In order to support the full functionality of the TestContext framework, a
  