# 2025-01-01 ## 2025-01-01 This release introduces performance improvements for Cover Reports, improved Test Review diff options and the ability to prevent Cover from writing tests which call specific methods. It also resolves various issues with the CLI and Plugin. ## Important Notices ### Changes to test code * **Test Method Ordering**: In an upcoming release, Cover will adjust test method ordering and imports for inner classes. This will cause a one-time churn, resulting in larger-than-usual diffs in your test code. * **Test Method Tagging**: In an upcoming release, tests created by Cover will be annotated with a `MaintainedByDiffblue` label. This will cause a one-time churn when recreating test, resulting in larger-than-usual diffs in your test code. This will enable Cover to combine Diffblue tests and manually written tests into the same test classes. ### Requirements * **JUnit 4**: Users of JUnit 4 will soon require the use of the [`cover-annotations` library](https://docs.diffblue.com/features/cover-annotations) version `1.3.0+` in order for coverage to be calculated correctly. This will be part of Test Method Tagging. ### Diffblue Cover is now generally available to individual developers and small teams. We've [just launched](https://www.diffblue.com/resources/diffblue-cover-is-now-generally-available-to-individual-developers/) our Developer Edition license. From today, individual developers can leverage the power of AI they can trust for unit test generation and maintenance. ### Enhancements * Cover now supports Jupiter 5.11.4. \[Ref: TG-22497] * Reports: Telemetry page performance improvements. \[Ref: TG-22415] * Plugin: Cover now allows the Test Review window to be expanded/docked for easier test diff reviewing. \[Ref: TG-22378] * CLI: Cover now allows excluding methods from being called in tests by using the `--exclude-method` option. \[Ref: TG-22235] ### Resolved Issues * Plugin: Resolved an issue which prevented the 'What's New' page from loading on Windows following an upgrade. \[Ref: TG-22495] * Resolved an issue which caused Cover to report `R026` while writing tests due to custom base classes not being considered. \[Ref: TG-22341] * Plugin: Resolved an issue which caused cover to show 'delete test' gutter icons on non-test methods. \[Ref: TG-22177] * Resolved an issue which caused Cover to write non-compiling tests for overloaded methods with variadic parameters (varargs). \[Ref: TG-21835] ### 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] --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://cover-docs-preview.diffblue.com/updates-and-upgrades/release-archive/2025-01-01.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.