Diffblue Cover Reports, our tool providing data visualizations, has been updated to tell you when your report upload has been successful, and provide a link directly to that report. This applies to both uploading an existing report, and to creating and then uploading a new report. Please see here for our documentation on using Diffblue Cover Reports.
Following on from our previous update, providing a link to the method under test in the Javadoc of the test methods, we have now improved the Javadoc links for interfaces and combined tests.
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.
- Cover now includes an improved Javadoc for tests it has written. [Ref: TG-16865]
- CLI: Cover now provides additional logging when providing custom test inputs via
Propertiesinstances. [Ref: TG-16957]
- CLI: Cover now provides improved messaging whilst uploading test creation reports, via the
createoptions, to Cover Reports. [Ref: TG-16746]
- Resolved an issue which caused non-compiling tests to be written due to mocks using wildcard generics. [Ref: TG-16852]
- Resolved an issue which, in some circumstances, caused insufficient remediation advice to be available when incomplete tests were written by Cover (due to the failure to create a Spring context). [Ref: TG-16804]
- CLI: Resolved an issue which prevented absolute paths being handled correctly whilst providing custom test inputs via
DiffblueRules.yml. [Ref: TG-16973]
- IntelliJ Plugin: Resolved an issue which caused a spurious
Unsupported Java Language Versionwarning to be logged whilst using some versions of Java 17. [Ref: TG-16956]
- IntelliJ Plugin: Resolved an issue which caused 'Registered to' field to show
null null <null>on the 'Diffblue Cover License' window whilst using a Community Edition license. [Ref: TG-16953]
- CLI: The command
dcover clean --failingdoes not work on Gradle projects. This command is now deprecated and
dcover validateshould be used instead. [Ref: TG-11707]