anchor.diff:  `custom` strategy.
   
   To select a strategy, set the `junit.jupiter.execution.parallel.config.strategy`
  -configuration parameter to one of the following options:
  +configuration parameter to one of the following options.
   
   `dynamic`::
     Computes the desired parallelism based on the number of available processors/cores
  
positive.code: specific shared resource that requires synchronized access to ensure reliable test
  execution. The shared resource is identified by a unique name which is a `String`. The
  name can be user-defined or one of the predefined constants in `{Resources}`:
  `SYSTEM_PROPERTIES`, `SYSTEM_OUT`, or `SYSTEM_ERR`.
  
  If the tests in the following example were run in parallel _without_ the use of
  {ResourceLock}, they would be _flaky_. Sometimes they would pass, and at other times they
  
negative.code: example, in `junit-platform.properties` (see <<running-tests-config-params>> for other
  options).
  
  Please note that enabling this property is only the first step required to execute tests
  in parallel. If enabled, test classes and methods will still be executed sequentially by
  default. Whether or not a node in the test tree is executed concurrently is controlled by
  its execution mode. The following two modes are available.
  
  `SAME_THREAD`::
    Force execution in the same thread used by the parent. For example, when used on a test
  