anchor.diff:  	}
   ----
   
  -* `@Rollback`
  -
  -+
  -
  -Indicates whether the transaction for a transactional test method should be __rolled
  -back__ after the test method has completed. If `true`, the transaction is rolled back;
  -otherwise, the transaction is committed (see also `@Commit`). Rollback semantics for
  -integration tests in the Spring TestContext Framework default to `true` even if
  +===== @Rollback
  +`@Rollback` indicates whether the transaction for a transactional test method should be
  +__rolled back__ after the test method has completed. If `true`, the transaction is rolled
  +back; otherwise, the transaction is committed (see also `@Commit`). Rollback semantics
  +for integration tests in the Spring TestContext Framework default to `true` even if
   `@Rollback` is not explicitly declared.
  -
  -+
   
   When declared as a class-level annotation, `@Rollback` defines the default rollback
   semantics for all test methods within the test class hierarchy. When declared as a
   method-level annotation, `@Rollback` defines rollback semantics for the specific test
   method, potentially overriding class-level `@Rollback` or `@Commit` semantics.
   
  -+
  -
   [source,java,indent=0]
   [subs="verbatim,quotes"]
   ----
  
positive.code: 	}
  ----
  
  * `@DirtiesContext`
  
  +
  
  Indicates that the underlying Spring `ApplicationContext` has been __dirtied__ during
  the execution of a test (i.e., modified or corrupted in some manner -- for example, by
  changing the state of a singleton bean) and should be closed. When an application
  context is marked __dirty__, it is removed from the testing framework's cache and
  closed. As a consequence, the underlying Spring container will be rebuilt for any
  subsequent test that requires a context with the same configuration metadata.
  
  +
  
  `@DirtiesContext` can be used as both a class-level and method-level annotation within
  the same class or class hierarchy. In such scenarios, the `ApplicationContext` is marked
  as __dirty__ before or after any such annotated method as well as before or after the
  current test class, depending on the configured `methodMode` and `classMode`.
  
  +
  
  The following examples explain when the context would be dirtied for various
  configuration scenarios:
  
  +
  
  ** Before the current test class, when declared on a class with class mode set to
  `BEFORE_CLASS`.
  
  +
  
negative.code: 	}
  ----
  
  ===== @Sql
  `@Sql` is used to annotate a test class or test method to configure SQL scripts to be
  executed against a given database during integration tests.
  
  [source,java,indent=0]
  [subs="verbatim,quotes"]
  