anchor.diff:  
   === Test case filtering.
   
  -- `tests.class` is a class-filtering shell-like glob pattern,
  -- `tests.method` is a method-filtering glob pattern.
  -
  -Run a single test case (variants)
  +You can run a single test, provided that you specify the Gradle project.  See the documentation on
  +https://docs.gradle.org/current/userguide/userguide_single.html#simple_name_pattern[simple name pattern filtering].
  +
  +Run a single test case in the `server` project:
   
   ----------------------------------------------------------
  -./gradlew test -Dtests.class=org.elasticsearch.package.ClassName
  -./gradlew test "-Dtests.class=*.ClassName"
  +./gradlew :server:test --tests org.elasticsearch.package.ClassName
   ----------------------------------------------------------
   
  -Run all tests in a package and its sub-packages
  +Run all tests in a package and its sub-packages:
   
   ----------------------------------------------------
  -./gradlew test "-Dtests.class=org.elasticsearch.package.*"
  +./gradlew :server:test --tests 'org.elasticsearch.package.*'
   ----------------------------------------------------
  -
  -Run any test methods that contain 'esi' (like: ...r*esi*ze...)
  -
  --------------------------------
  -./gradlew test "-Dtests.method=*esi*"
  --------------------------------
   
   Run all tests that are waiting for a bugfix (disabled by default)
   
  
positive.code: ----------------------------
  
  Its difficult to pick the "right" number here. Hypercores don't count for CPU
  intensive tests and you should leave some slack for JVM-interal threads like
  the garbage collector. And you have to have enough RAM to handle each JVM.
  
  === Test compatibility.
  
negative.code: (derived from a single random master seed).
  
  --------------------------------------------------
  ./gradlew :server:test -Dtests.iters=N --tests org.elasticsearch.package.ClassName
  --------------------------------------------------
  
  === Repeats _all_ tests of ClassName N times.
  