2022-12-02
Last updated
Last updated
Diffblue Cover now supports IntelliJ IDEA 2022.3 (Community and Ultimate). In keeping with our policy of supporting the current and previous release, Diffblue Cover now supports IntelliJ IDEA 2022.3 and 2022.2. Support for IntelliJ IDEA 2022.1 has been removed as of Diffblue Cover 2022.12.01.
Four new features - Reports, Optimize, Refactor and Replay - have been added in this release of Diffblue Cover. In addition to autonomously writing and maintaining entire unit test suites without developer intervention, Cover Enterprise Edition now enables you to:
Automatically refactor Java code to improve testability
Slash the time and cost to run tests in Continuous Integration
Understand test coverage and code risk across your organization
Automatically shift complex functional tests left into unit test suites
Read this blog post or watch this short YouTube playlist to learn more about the new features. Then if you're interested in how the power of Enterprise Edition could help your team, get in touch via our website.
{: width="908" height="251"}
We are delighted to now offer a 14-day trial version of our Developer Edition, which includes the Diffblue Cover CLI, as part of our new licensing option. We're really excited that you can now "try before you buy"! To download your trial of Diffblue Cover Developer Edition, please click here. Full information on all our options is also available here.
Use Diffblue Cover on any CI platform to automatically update your unit tests and catch regressions for every commit - watch this video to learn more.
Reports: Improved responsiveness and usability of charts on the 'Output Codes' tab. [Ref: TG-18322]
Reports: Class/Package name widgets, on the 'Overview' tab, have been replaced with a pie chart showing 'coverage sources'. [Ref: TG-17390]
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]
