anchor.diff:  
   +
   
  -Resource locations are typically XML configuration files located in the classpath;
  -whereas, annotated classes are typically `@Configuration` classes. However, resource
  -locations can also refer to files in the file system, and annotated classes can be
  -component classes, etc.
  +Resource locations are typically XML configuration files or Groovy scripts located in
  +the classpath; whereas, annotated classes are typically `@Configuration` classes. However,
  +resource locations can also refer to files and scripts in the file system, and annotated
  +classes can be component classes, etc.
   
   +
   
  
positive.code: can also be configured via application context `initializers`.
  
  The following sections explain how to configure an `ApplicationContext` via XML
  configuration files, annotated classes (typically `@Configuration` classes), or context
  initializers using Spring's `@ContextConfiguration` annotation. Alternatively, you can
  implement and configure your own custom `SmartContextLoader` for advanced use cases.
  
  [[testcontext-ctx-management-xml]]
  ===== Context configuration with XML resources
  
negative.code: mapping files, and incurring that cost before running every test in every test fixture
  leads to slower overall test runs that reduce developer productivity.
  
  Test classes typically declare either an array of __resource locations__ for XML or Groovy
  configuration metadata -- often in the classpath -- or an array of __annotated classes__
  that is used to configure the application. These locations or classes are the same as or
  similar to those specified in `web.xml` or other configuration files for production
  deployments.
  
  By default, once loaded, the configured `ApplicationContext` is reused for each test.
  Thus the setup cost is incurred only once per test suite, and subsequent test execution
  