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: `/test-data.sql` script) are automatically rolled back by the
  `TransactionalTestExecutionListener` (see <<testcontext-tx,transaction management>> for
  details).
  
  
  [[testcontext-parallel-test-execution]]
  
negative.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 individual SQL statements or the resource paths to SQL scripts that should be
  run against a given database before or after an integration test method. Support for
  `@Sql` is provided by the `SqlScriptsTestExecutionListener`, which is enabled by default.
  
  NOTE: Method-level `@Sql` declarations override class-level declarations by default. As
  of Spring Framework 5.2, however, this behavior may be configured per test class or per
  test method via `@SqlMergeMode`. See
  <<testcontext-executing-sql-declaratively-script-merging>> for further details.
  
  [[testcontext-executing-sql-declaratively-script-resources]]
  ====== Path Resource Semantics
  
  Each path is interpreted as a Spring `Resource`. A plain path (for example,
  