anchor.diff:  initializers, respectively, for the test class shadow and effectively replace the
   configuration defined by superclasses.
   
  +NOTE: As of Spring Framework 5.3, test configuration may also be inherited from enclosing
  +classes. See <<testcontext-junit-jupiter-nested-test-configuration>> for details.
  +
   In the next example, which uses XML resource locations, the `ApplicationContext` for
   `ExtendedTest` is loaded from `base-config.xml` and `extended-config.xml`, in that order.
   Beans defined in `extended-config.xml` can, therefore, override (that is, replace) those
  
positive.code: If the `inheritLocations` or `inheritProperties` attribute in `@TestPropertySource` is
  set to `false`, the locations or inlined properties, respectively, for the test class
  shadow and effectively replace the configuration defined by superclasses.
  
  In the next example, the `ApplicationContext` for `BaseTest` is loaded by using only the
  `base.properties` file as a test property source. In contrast, the `ApplicationContext`
  
negative.code: automatically inherit the `@ActiveProfiles` configuration from the base class. In the
  following example, the declaration of `@ActiveProfiles` (as well as other annotations)
  has been moved to an abstract superclass, `AbstractIntegrationTest`:
  
  NOTE: As of Spring Framework 5.3, test configuration may also be inherited from enclosing
  classes. See <<testcontext-junit-jupiter-nested-test-configuration>> for details.
  
  [source,java,indent=0,subs="verbatim,quotes",role="primary"]
  .Java
  