anchor.diff:  <<testcontext-junit4-runner,SpringRunner>>, <<testcontext-junit4-rules,Spring's JUnit
   rules>>, or <<testcontext-support-classes-junit4,Spring's JUnit 4 support classes>>.
   
  -* `@IfProfileValue`
  -
  -+
  -
  -Indicates that the annotated test is enabled for a specific testing environment. If the
  -configured `ProfileValueSource` returns a matching `value` for the provided `name`, the
  -test is enabled. Otherwise, the test will be disabled and effectively _ignored_.
  -
  -+
  +===== @IfProfileValue
  +`@IfProfileValue` indicates that the annotated test is enabled for a specific testing
  +environment. If the configured `ProfileValueSource` returns a matching `value` for the
  +provided `name`, the test is enabled. Otherwise, the test will be disabled and
  +effectively _ignored_.
   
   `@IfProfileValue` can be applied at the class level, the method level, or both.
   Class-level usage of `@IfProfileValue` takes precedence over method-level usage for any
  
positive.code: 
  [[integration-testing-annotations-meta]]
  ==== Meta-Annotation Support for Testing
  Since Spring Framework 4.0, it is possible to use test-related annotations as
  <<beans-meta-annotations,meta-annotations>> in order to create custom _composed annotations_
  and reduce configuration duplication across a test suite.
  
  Each of the following may be used as meta-annotations in conjunction with the
  <<testcontext-framework,TestContext framework>>.
  
negative.code: 		// some logic that results in the Spring container being dirtied
  	}
  ----
  
  If `@DirtiesContext` is used in a test whose context is configured as part of a context
  hierarchy via `@ContextHierarchy`, the `hierarchyMode` flag can be used to control how
  