anchor.diff:  
   In addition to instructing the platform which test classes and test engines to include,
   which packages to scan, etc., it is sometimes necessary to provide additional custom
  -configuration parameters that are specific to a particular test engine. For example, the
  -JUnit Jupiter `TestEngine` supports _configuration parameters_ for the following use
  -cases.
  +configuration parameters that are specific to a particular test engine or registered
  +extension. For example, the JUnit Jupiter `TestEngine` supports _configuration
  +parameters_ for the following use cases.
   
   - <<writing-tests-test-instance-lifecycle-changing-default>>
   - <<extensions-registration-automatic-enabling>>
  
positive.code: 
  - `+**/Test*.java+`
  - `+**/*Test.java+`
  - `+**/*TestCase.java+`
  
  Note, however, that you can override this default behavior by configuring explicit
  
negative.code: [[running-tests-build-maven-config-params]]
  ===== Configuration Parameters
  
  You can set JUnit Platform <<running-tests-config-params, configuration parameters>> to
  influence test discovery and execution by declaring the `configurationParameters`
  property and providing key-value pairs using the Java `Properties` file syntax (as shown
  below) or via the `junit-platform.properties` file.
  
  [source,xml,indent=0]
  ----
  