anchor.diff:  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}`).
  +Invoking `gradlew junitPlatformTest` (or `gradlew test`) from the command line will
  +execute all tests within the project whose class names match the regular expression
  +supplied via the `includeClassNamePattern` (which defaults to
  +`{standard-include-class-name-pattern}`).
   
   Executing the `junitPlatformTest` task in the `{junit5-gradle-consumer}` project results
   in output similar to the following:
  
positive.code: `@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.
  
  [source,java,indent=0]
  [subs="verbatim"]
  
negative.code: ----
  
  [[running-tests-build-maven-filter-tags]]
  ===== Filtering by tags
  
  You can filter tests by tags using the following configuration properties.
  
  - to include a tag, use either `groups` or `includeTags`
  - to exclude a tag, use either `excludedGroups` or `excludeTags`
  
  [source,xml,indent=0]
  [subs="verbatim,attributes"]
  