> For the complete documentation index, see [llms.txt](https://cover-docs.diffblue.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cover-docs.diffblue.com/updates-and-upgrades/release-archive/2025-01-02.md).

# 2025-01-02

## 2025-01-02

This release improves the Plugin's Test Review functionality, adds a `MaintainedByDiffblue` annotation for tests written by Cover and provides improved guidance to help avoid Spring context initialization failures. It also resolves various issues with the CLI and Plugin.

## Important Notices

### Changes to test code

* **Test Method Ordering**: In this release, Cover adjusts 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 this release, tests created by Cover will be annotated with a `MaintainedByDiffblue` label. This will cause a one-time churn when recreating tests, 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 in a future release.

### 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 shows a warning if PowerMock is detected in the project under test, as Cover currently has limited support for it. \[Ref: TG-22527]
* Cover now provides guidance around classes to mock statically, with a `DiffblueBase` class, to help avoid Spring context initialization failures. \[Ref: TG-22342]
* Cover now writes tests with a `MaintainedByDiffblue` annotation if the `cover-annotations` library is available. \[Ref: TG-21448]
* Plugin: Cover's Test Review feature now provides a warning if unreviewed tests will be lost when closing the Test Review panel. \[Ref: TG-21295]

### Resolved Issues

* CLI: Resolved an issue which, in some circumstances, caused Cover to show `F009: Internal error` while running `dcover create --preflight`. \[Ref: TG-22438]
* Plugin: Resolved an issue in Test Review which, in some circumstances, could cause Cover to report an incorrect number of tests to be reviewed for a class. \[Ref: TG-22081]

### 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]