2026-07-01
This release adds support for IntelliJ IDEA 2026.2. Thanks to the open-ended IntelliJ IDEA version support introduced in 2026.05.01, existing plugin installations already work with IntelliJ IDEA 2026.2 without needing to upgrade Cover. This release also retires the Community Support Forum.
Important Notices
Retirement of the Community Support Forum: The Diffblue Community Support Forum has been decommissioned. The plugin no longer includes a 'Community Support Forum' menu item, and references to the forum have been removed. For help, see the Diffblue Docs or the Diffblue Support page.
Deprecation of Docker Hub distribution for Cover CLI: Diffblue Cover images are no longer published to Docker Hub. Users who previously pulled the
diffblue/cover-cliimage from Docker Hub will no longer receive new tags there and should obtain Cover CLI through the standard release channels.
Enhancements
Plugin: Diffblue Cover now supports IntelliJ IDEA 2026.2. Existing plugin installations already work with IntelliJ IDEA 2026.2 due to the open-ended version support introduced in 2026.05.01. [Ref: TG-24169]
Resolved Issues
Upgraded Bouncy Castle to address security vulnerability CVE-2025-14813.
Known Issues
Plugin: Diffblue Cover incorrectly displays a menu option to write tests for existing test files. [Ref: TG-17163]
Using JDKs other than the supported Open JDK and Oracle JDK may produce unexpected results due to implementation differences. [Ref: TG-19345]
Cover may encounter an
F009(Internal error) caused by aClassCircularityErrorinvolvingorg/mockito/configuration/MockitoConfigurationwhen writing tests with Mockito 5. The recommended workaround is to downgrade to Mockito 4.x. [Ref: TG-19610]Reports: The total line count metric in Reports only includes Java code. Kotlin code is not included. [Ref: TG-22088]
Reports: Total lines of code metric can incorrectly count a multi-line comment at the end of a line of code, resulting in fewer than expected lines counted. [Ref: TG-22089]
Reports: Following an upgrade, the 'Total Lines of Code' card may show 0 until a new reports bundle has been uploaded. [Ref: TG-22094]
Cover may write more simplistic tests with less meaningful assertions when Spring Boot dependency injection is disabled. [Ref: TG-22102]
In some circumstances, Cover will still write Spring Boot tests when Spring Boot dependency injection is disabled. [Ref: TG-22103]
Cover may write failing TestNG tests when Spring Boot dependency injection is disabled. [Ref: TG-22107]
Plugin: On some displays, the Test Review subsection title 'Tests for review' is malformed. [Ref: TG-22805]
When test formatting settings are changed, the Test Review feature may incorrectly remove the
@ManagedByDiffblueannotation from tests, particularly in cases involving static import formatting changes. [Ref: TG-23750]Plugin: Using the Test Review feature may create tests that have incompatible dependency injection systems. [Ref: TG-23935]
CLI: In rare circumstances, Cover may remove existing tests when using merge mode (
--merge). The recommended workaround is to use the@WriteTestsToannotation to specify a separate test class. [Ref: TG-24166]Plugin: When writing tests for a project that targets a JDK version newer than IntelliJ's runtime JDK (e.g., Java 25 with IntelliJ's bundled Java 21), generated tests may not match the project's non-default formatting style and will instead use default IntelliJ formatting. [Ref: TG-24168]
Last updated
Was this helpful?

