anchor.diff:  strategy with a factor of `1`. Consequently, the desired parallelism will be equal to the
   number of available processors/cores.
   
  +.Parallelism does not imply maximum number of concurrent threads
   NOTE: JUnit Jupiter does not guarantee that the number of concurrently executing tests
   will not exceed the configured parallelism. For example, when using one of the
   synchronization mechanisms described in the next section, the `ForkJoinPool` that is used
  
positive.code: [[writing-tests-parallel-execution]]
  === Parallel Execution
  
  By default, JUnit Jupiter tests are run sequentially in a single thread. Running tests in
  parallel -- for example, to speed up execution -- is available as an opt-in feature since
  version 5.3. To enable parallel execution, set the
  
negative.code: [[writing-tests-parallel-execution-synchronization]]
  ==== Synchronization
  
  In addition to controlling the execution mode using the `{Execution}` annotation, JUnit
  Jupiter provides another annotation-based declarative synchronization mechanism. The
  `{ResourceLock}` annotation allows you to declare that a test class or method uses a
  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
  