anchor.diff:  	}
   ----
   
  +[[testcontext-executing-sql-declaratively-script-execution-phases]]
   ====== Script Execution Phases
   
   By default, SQL scripts are executed before the corresponding test method. However, if
  
positive.code: In addition to the aforementioned mechanisms for running SQL scripts programmatically,
  you can declaratively configure SQL scripts in the Spring TestContext Framework.
  Specifically, you can declare the `@Sql` annotation on a test class or test method to
  configure the resource paths to SQL scripts that should be run against a given database
  before or after an integration test method. Note that method-level declarations override
  class-level declarations and that support for `@Sql` is provided by the
  `SqlScriptsTestExecutionListener`, which is enabled by default.
  
  ====== Path Resource Semantics
  
  Each path is interpreted as a Spring `Resource`. A plain path (for example,
  
negative.code: `/test-data.sql` script) are automatically rolled back by the
  `TransactionalTestExecutionListener` (see <<testcontext-tx,transaction management>> for
  details).
  
  [[testcontext-executing-sql-declaratively-script-merging]]
  ====== Merging and Overriding Configuration with `@SqlMergeMode`
  
  As of Spring Framework 5.2, it is possible to merge method-level `@Sql` declarations with
  class-level declarations. For example, this allows you to provide the configuration for a
  database schema or some common test data once per test class and then provide additional,
  use case specific test data per test method. To enable `@Sql` merging, annotate either
  your test class or test method with `@SqlMergeMode(MERGE)`. To disable merging for a
  specific test method (or specific test subclass), you can switch back to the default mode
  via `@SqlMergeMode(OVERRIDE)`. Consult the <<spring-testing-annotation-sqlmergemode,
  `@SqlMergeMode` annotation documentation section>> for examples and further details.
  
  
  [[testcontext-parallel-test-execution]]
  