anchor.diff:  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.
  +configuration files, Groovy scripts, 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
  
positive.code: 	}
  ----
  
  It is also possible to omit the declaration of XML configuration files or annotated
  classes in `@ContextConfiguration` entirely and instead declare only
  `ApplicationContextInitializer` classes which are then responsible for registering beans
  in the context -- for example, by programmatically loading bean definitions from XML
  files or configuration classes.
  
negative.code: 
  +
  
  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.
  
  +
  
  