anchor.diff:  `@RunWith(JUnitPlatform.class)` directly. Please note that the test methods in the
   following example are annotated with `org.junit.jupiter.api.Test` (JUnit Jupiter), not
   `org.junit.Test` (JUnit Vintage). Moreover, in this case the test class must be `public`;
  -otherwise, IDEs won't recognize it as a test class.
  +otherwise, IDEs won't recognize it as a JUnit 4 test class.
   
   [source,java,indent=0]
   [subs="verbatim"]
  
positive.code: Once the JUnit Gradle plugin has been applied and configured, you have a new
  `junitPlatformTest` task at your disposal.
  
  Invoking `gradlew clean junitPlatformTest` (or `gradlew clean test`) from the command
  line will execute all tests within the project whose class names match the regular
  expression supplied via `includeClassNamePattern` (defaults to `{standard-include-class-name-pattern}`).
  
  Executing the `junitPlatformTest` task in the `{junit5-gradle-consumer}` project results
  in output similar to the following:
  
negative.code: ----
  
  Setting `logManager` instructs the JUnit Gradle plugin to set the
  `java.util.logging.manager` system property to the supplied _fully qualified class_ name
  of the `java.util.logging.LogManager` implementation to use. The above example
  demonstrates how to configure log4j as the `LogManager`.
  
  By default, the JUnit Gradle plugin disables the standard Gradle `test` task, but this
  can be overridden via the `enableStandardTestTask` flag.
  
  [[running-tests-build-gradle-selectors]]
  ===== Configuring Selectors
  
  By default, the plugin will scan your project's output directories for tests. However,
  you can specify which tests to execute explicitly using the `selectors` extension element.
  
  [source,java,indent=0]
  [subs="verbatim,attributes"]
  