anchor.diff:  
   ===== Bug Fixes
   
  -* Maven Surefire: Ensure failed tests of test engines that do not use `MethodSource` (e.g.
  -  Spek) are reported correctly.
  -* Maven Surefire: In some cases, tests writing to `System.out` or `System.err`, in
  -  particular via a logging framework, were not reported correctly when executed with a
  -  non-zero `forkCount`.
  +* Failed tests are now reported correctly with Maven Surefire for test engines that do
  +  not use `MethodSource` (e.g. Spek).
  +* Tests that write to `System.out` or `System.err`, in particular via a logging
  +  framework, are now consistently reported correctly when executed with a non-zero
  +  `forkCount` with Maven Surefire.
   
   ===== Deprecations and Breaking Changes
   
  
positive.code:   for this information.
  * Class loading errors that occur during classpath scanning are now logged at `DEBUG`
    level (i.e., the `FINE` log level in `java.util.logging`) instead of as warnings.
  * New discovery selector `ModuleSelector` for scanning Java 9 modules for test classes.
  * New console launcher option `--select-module <name>` or `-o <name>`.
  * New console launcher option `--scan-module-path` for selecting all resolved modules
    available on the boot layer configuration.
  * Maven Surefire: Add support for the `redirectTestOutputToFile` feature.
  * Maven Surefire: Accept and ignore empty strings for `<includeTags/>`, `<groups/>`,
    `<excludeTags/>` and `<excludedGroups/>`.
  
  [[release-notes-5.1.0-junit-jupiter]]
  ==== JUnit Jupiter
  
negative.code:   - For example, code such as
      `store.getOrComputeIfAbsent(X.class, key \-> new X(), X.class)` can now replaced with
      `store.getOrComputeIfAbsent(X.class)`.
  * The `JupiterTestEngine` supports the new JUnit Platform `ModuleSelector` for selecting
    Java 9 modules.
    - This is an alternative to the existing classpath scanning support.
  
  
  [[release-notes-5.1.0-junit-vintage]]
  