Dedicated User and Support Log Files
Release date: Sep 12, 2022
Enhanced log files for efficient technical support
Efficient support for all types of technical issues, user queries and errors is now facilitated with our dedicated support log file system.
We have separated log files into two specific flavors: User log files contain details necessary to understand and remedy common configuration and build issues; Support log files contain extra debug information, which will enable our technical support team to more efficiently respond to queries.
Our user logs are clearer and thorough, making it easy to find the answer you need.
Environment issue resolution suggestions reported in console output
Some issues in your project build and test framework can be hard to diagnose - resulting in slow builds, failing tests, or errors while running your project.
Now you get helpful information about common build and test framework issues in the console output to resolve common set-up problems.
Meet the Diffblue team at Devoxx in October
Diffblue are delighted to be sponsoring Devoxx Belgium 2022. Our team can’t wait to talk about AI for Code with the Java development community.
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
Cover’s logging is now separated into user-focused and support-focused files to improve readability. [Ref: TG-17716]
CLI: Cover now considers Maven wrappers and local Gradle installations correctly. [Ref: TG-17658]
CLI: Cover now provides improved output during environment checks. [Ref: TG-17562]
Resolved an issue which caused Cover to log an
Error, rather than a
Warning, when a patch file which does not modify any classes, or an empty patch file, is used with
--patch-only. [Ref: TG-17711]
Resolved an issue which, in some circumstances, caused Cover to not write tests because of
@Valueannotated arrays. [Ref: TG-17698]
Resolved an issue which caused Cover to incorrectly mock functional interfaces in Spring integration tests. [Ref: TG-17689]
- 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]