This release adds support for Jakarta EE Dependency Injection and enhances baseline test coverage capabilities for Cover Reports. See the full Release Notes below for details of all enhancements and resolved issues covered by this release.


  • CLI & Plugin: Diffblue Cover now supports writing tests for Jakarta EE Dependency Injection for Java EE 8/Jakarta EE 8 and Jakarta EE 9. Note: Diffblue Cover does not use Jakarta EE application context for tests, all injected dependencies will be mocked. [Ref: TG-19392]

  • Reports: Cover Reports can now visualize test coverage of projects without needing to write tests via dcover create first. [Ref: TG-18569]

Resolved Issues

  • CLI & Plugin: Resolved an issue which caused Diffblue Cover to report R026: Failed to create Spring context if the Scala standard library is in use. [Ref: TG-19448]

  • CLI: Resolved an issue which caused Diffblue Cover to report F009: Internal error when providing an invalid Cover Reports server location. Diffblue Cover now reports E138: Unable to convert path to URL. [Ref: TG-19400]

  • Reports: Resolved a minor issue with the page navigation on the Projects page. [Ref: TG-19375]

  • Optimize: Resolved an issue which caused Diffblue Cover to log a NullPointerException when using a patch which contains a file path which cannot be found. Diffblue Cover now reports E124: Referenced file in patch file not found. [Ref: TG-19373]

  • CLI & Plugin: Improved E013: Compatible launcher not found output code messaging (JUnit Jupiter Launcher and JUnit Jupiter Engine version compatibility). [Ref: TG-19338]

  • Cover: Improved L024: Unexpected licensing exception output code messaging (licensing server connection). [Ref: TG-19280]

  • CLI & Plugin: Introduced a recommendation to avoid JUnit 4.11 and below when using JUnit Vintage Engine. Also recommend to avoid JUnit Vintage Engine when JUnit 5 is not present. [Ref: TG-19220]

Known Issues

  • Cover may produce tests for JUnit 4.10 and lower that do not compile due to the use of assertNotEquals. [Ref: TG-17605]

  • IntelliJ Plugin: Upgrading to IntelliJ IDEA 2022.3 may, in some circumstances, cause existing run configurations to no longer produce tests. Removing any run configurations for that entity and writing tests again will recreate a working run configuration [Ref: TG-18282]

Last updated