anchor.diff:  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.
  +
  +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, the `ApplicationContext` for `BaseTest` is loaded by using only the
   `base.properties` file as a test property source. In contrast, the `ApplicationContext`
  
positive.code: initializers, respectively, for the test class shadow and effectively replace the
  configuration defined by superclasses.
  
  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
  
negative.code: 
  
  NOTE: `@ActiveProfiles` provides support for inheriting active bean definition profiles
  declared by superclasses and enclosing classes by default. You can also resolve active
  bean definition profiles programmatically by implementing a custom
  <<testcontext-ctx-management-env-profiles-ActiveProfilesResolver, `ActiveProfilesResolver`>>
  and registering it by using the `resolver` attribute of `@ActiveProfiles`.
  
  See <<testcontext-ctx-management-env-profiles>>,
  <<testcontext-junit-jupiter-nested-test-configuration>>, and the
  {api-spring-framework}/test/context/ActiveProfiles.html[`@ActiveProfiles`] javadoc for
  examples and further details.
  
  