Updated test writing limits
Release date: Nov 22, 2021
Updated test writing limits!
Diffblue is delighted to announce that we have been able to DOUBLE test writing limits for all versions. This means the daily writing limits are now as listed below:
|Community Edition (IntelliJ Plugin only)||Developer Edition||DevOps Edition||Standard Edition||Enterprise Edition|
|200 tests per day / per user||500 tests per day / per user||10,000 tests per day, per pool of 10 users||Unlimited||Unlimited|
Diffblue Cover creates and maintains a log file to assist you with understanding behavior and for debugging purposes. In this release, the log file has been updated to show which options were used for all DCover commands.
The IntelliJ Plugin has also been updated so that users can now easily access the log file by clicking a link in the editor.
New Developer Edition trial available
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.
How do I automatically maintain all of these tests?
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.
Full Release Notes
Enterprise Edition: Cover now supports offline license activation and offline usage. [Ref: TG-15430]
CLI: Cover now prefers Gradle, over Maven, when both Gradle and Maven build environments are present.
--mavencan be used to select the environment you want to use. [Ref: TG-15569]
Cover now attempts to automatically load dependencies if Spring fails to load due to a missing dependency injection. [Ref: TG-15707]
IntelliJ Plugin: Clicking on the log file name now allows viewing the log file by opening it with the standard application configured for
.logfiles. [Ref: TG-15392]
CLI: Cover now includes the command line arguments passed to
dcoverin its log files for easier debugging. [Ref: TG-15784]
coverage-diffcommand has been removed. Users of
coverage-diffshould migrate to Cover Reports. See here for details on getting started with Cover Reports. [Ref: TG-15835]
Reports: Resolved an issue which caused error messages, related to report uploading, to not be shown. [Ref: TG-15891]
IntelliJ Plugin: Resolved an issue which caused a misleading spinning icon to be shown next to ‘Writing Tests’, in the Diffblue Cover Tool Window, after cancelling an invocation of Write Tests. [Ref: TG-15742]
dcover clean --failingdoes not work on Gradle projects. [Ref: TG-11707]
Diffblue Cover was unable to create an indexerror may appear if switching projects happens before Cover has finished indexing. [Ref: TG-13772]