2025-02-01
2025-02-01
This release includes enhancements and resolves issues for the CLI and IntelliJ plugin. Key improvements include resolving an issue where String values could be incorrectly mocked as dependencies, and the introduction of a template DiffblueBuild.yaml file for Ant projects, simplifying setup.
Important Notices
Updated Test Creation Limits for Diffblue Cover
As of the 2025.02.01 release, we've updated how test creation limits work for Diffblue Cover to give you more predictable and manageable usage. These changes apply only to Community Edition and Developer Edition. Teams and Enterprise editions are unaffected.
What's Changed
Test creation limits are now based on methods tested, not individual tests written.
You will incur consumption for each method for which a new test is successfully produced. This means you have a clearer understanding of your limit usage before clicking 'write tests'.
Consumption is calculated based on the number of new methods covered by generated tests, regardless of how many tests are produced for a single method.
When Cover Plugin's 'Test Review' feature is enabled, quota consumption will still occur for methods with newly generated tests even if they are not "accepted".
Monthly Limits
Community Edition: 25 methods per month
Developer Edition Basic: 100 methods per month
Developer Edition Pro: 200 methods per month
Developer Edition Ultra: 400 methods per month
Diffblue Cover is now generally available to individual developers and small teams.
Enhancements
CLI: Cover now provides clearer messages if test validation takes too long. Instead of indicating a failed coverage calculation, it guides users to adjust the
TIMEOUTsetting inDiffblueBuild.yaml. [Ref: TG-22629]Cover now generates a template
DiffblueBuild.yamlfile for Ant projects when usingdcover build-default-config --ant. The template includes essential configurations and inline customization guidance, simplifying setup. [Ref: TG-22602]Plugin: The "Update Test" functionality now uses the
@MethodsUnderTesttest annotation for accurately identifying Methods Under Test (MuTs). Please avoid modifying this annotation. [Ref: TG-22462]CLI & Plugin: Cover now counts methods tested instead of tests created. This affects Community Edition, Developer Edition, and Teams Trial users. [Ref: TG-21883]
CLI:
dcover validatenow handles validation errors more precisely. Instead of discarding entire test classes due to issues in a subset of tests (compilation or assertion failures), it discards only the failing tests, preserving the rest. [Ref: TG-20316]
Resolved Issues
CLI: Resolved an issue where Cover incorrectly generated
@AfterMethodmethods for TestNG, preventing proper reset of mocks and the target object. [Ref: TG-22632]Resolved an issue which could cause Cover to incorrectly mock
Stringvalues as dependencies, potentially leading to invalid test code such as@MockBean private String string. [Ref: TG-22523]
Known Issues
Plugin: Cover incorrectly provides a menu option to write tests for a test file. [Ref: TG-17163]
Cover supports Open JDK and Oracle JDK; results with other JDKs may differ due to the variability in their implementations of Java. [Ref: TG-19345]
Reports: Cover only counts Java code towards the total line count metrics. Kotlin code is not currently included. [Ref: TG-22088]
Reports: Total lines of code metric can incorrectly count a multi-line comment at the end of a line of code, resulting in fewer than expected lines counted. [Ref: TG-22089]
Reports: Following an upgrade, the 'Total Lines of Code' card may show 0 until a new reports bundle has been uploaded. [Ref: TG-22094]
In some circumstances, Cover may write more simplistic tests with less meaningful assertions when Spring Boot dependency injection is disabled. [Ref: TG-22102]
In some circumstances, Cover will still write Spring Boot tests when Spring Boot dependency injection is disabled. [Ref: TG-22103]
Cover may write failing TestNG tests when Spring Boot dependency injection is disabled. [Ref: TG-22107]
Last updated
Was this helpful?