2022-03-01
Last updated
Last updated
This release, we have updated the Diffblue Cover IntelliJ plugin to include partial tests by default, resulting in more tests written. We have switched on the option of writing tests for enum values by default, too. We have also added a summary panel so you can easily see how many complete and partial tests have been written: {: width="735" height="306"} As shown in this image, you can click on Change Settings if you should want to turn off either of these new default options.
SonarQube is a tool to enforce coding practices to help developers write better code. Some of its rules have the purpose to detect common mistakes; others purely concern specific aspects of coding style. Some of the latter rules are a matter of taste and usually need to be tailored to the coding guidelines of a specific project. Using all rules may lead to lots of noisy warnings, and sometimes such warnings are triggered on tests created by Diffblue Cover.
This release, we have added the --annotate-suppress-warnings option, to reduce the warnings in the tests created by Diffblue Cover. Full details are in our documentation.
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.
IntelliJ Plugin: Cover now writes partial tests by default. Partial test writing can be configured via the Cover plugin settings. [Ref: TG-16578]
IntelliJ Plugin: Cover now provides a summary of tests written in the Diffblue Tool Panel. [Ref: TG-16577]
CLI: Cover now adds @SuppressWarning annotations to tests it writes when the --annotate-suppress-warnings CLI option is used. [Ref: TG-16611]
Cover now uses xml configuration for testing spring classes even if the spring-boot-test dependency is not present. [Ref: TG-16456]
CLI: Cover's test validation now supports projects that use the (Maven or Gradle) ignoreFailures feature. [Ref: TG-16104]
Resolved an issue which caused Cover to not detect calls to System.currentTimeMillis() in methods under test, in some circumstances, causing non-deterministic tests to be written. [Ref: TG-16643]
Test validation output has been improved in the case where some tests have been cleaned up and test validation still fails. [Ref: TG-16633]
Resolved an issue which, in some circumstances, caused Cover to not write tests for classes containing an @Value annotated field. [Ref: TG-16613]
CLI: Resolved an issue which caused Cover to report Cleaning tests failed rather than logging output code E087: Multiple testing frameworks when multiple test frameworks are available. [Ref: TG-16585]
CLI: Fixed incorrect descriptions for --name and --project options in Cover's man page and online help. [Ref: TG-16573]
CLI: Resolved an issue which caused Cover to not log the number of tests written per class to the log file while using --verbose. [Ref: TG-15145]
CLI: The command dcover clean --failing does not work on Gradle projects. This command is now deprecated and dcover validate should be used instead. [Ref: TG-11707]
