Writing unit tests has historically eaten a disproportionate share of developer time relative to how interesting the work is, which makes it a natural target for AI automation. The landscape here has shifted quickly, though, and the branded products worth knowing in 2026 aren’t always the ones that made headlines a year or two ago.
At a Glance
| Tool | Status | What it claims |
|---|---|---|
| Qodo Cover (open source) | Unmaintained since June 2025 | Aimed to increase code coverage; no benchmark numbers published in its own README |
| Qodo Gen | Active (current product) | Test generation folded into Qodo’s broader IDE extension and agentic platform |
| Diffblue Cover / Testing Agent | Active, vendor-marketed | Vendor claims 81% autonomous code coverage, “2.5x more than AI coding tools alone” |
Short Verdict
The open-source tool many articles still reference, Qodo Cover, is no longer maintained; current test-generation capability from that vendor now lives inside Qodo Gen. Diffblue is the more actively marketed standalone player, with bold coverage-percentage claims that come directly from the vendor’s own press materials rather than an independently replicated benchmark — worth treating as a starting point for your own evaluation, not a guarantee.
Qodo Cover Is Deprecated
Qodo Cover, the open-source CLI tool previously known as “cover-agent,” carries an explicit notice on its GitHub repository, dated June 15, 2025, stating the repository is no longer maintained. Its original README described the goal as helping “increase code coverage” but never published specific before/after coverage benchmark numbers. Current test-generation functionality from Qodo now lives in the “Qodo Gen” IDE extension, part of the same broader platform that sells Qodo Merge for code review (covered in our AI code review comparison). Anyone evaluating Qodo for test generation today should look at Qodo Gen’s current capabilities rather than referencing the archived Cover project as if it were still active.
Diffblue
Diffblue markets a “Testing Agent” product built around autonomous unit test generation for Java codebases. In its own press materials, the company states its Testing Agent “delivers 81% code coverage autonomously, 2.5x more than AI coding tools alone,” and separately claims a “20x productivity advantage” compared with AI coding assistants used for test writing. These are vendor-published marketing figures from Diffblue’s own press release, and we found no independent, third-party benchmark replicating them during this research. That doesn’t make them false, but it does mean they should be read as a claim to verify against your own codebase, not an externally audited result.
Why This Matters for Teams Evaluating These Tools
Automated test generation tools are judged almost entirely on coverage improvement and the quality of the tests they produce (do they actually catch regressions, or just pad a coverage metric), and vendors in this space have strong incentive to publish favorable numbers. The most reliable way to evaluate any of these tools is still a trial run against your own codebase, comparing coverage and mutation-testing results before and after, rather than taking a vendor’s published percentage as representative of your specific code.
Pros and Cons
- Qodo Gen pros: part of a broader, actively maintained agentic platform with IDE integration. Cons: test-generation-specific pricing isn’t broken out separately from Qodo’s general credit-based plans.
- Diffblue pros: focused specifically on autonomous Java unit test generation, actively marketed and developed. Cons: headline coverage and productivity figures are vendor-published, not independently verified; no public pricing page was found during this research.
Who It’s a Good Fit For
Teams already using Qodo for code review should evaluate Qodo Gen’s test-generation features as a natural extension rather than looking for the now-unmaintained Qodo Cover. Java-heavy teams specifically interested in autonomous unit test generation as a standalone capability are the target audience for Diffblue, though they should request a trial and measure results against their own codebase before trusting the vendor’s published figures.
Bottom Line
AI test generation is a real and fast-moving category, but branding has shifted quickly (Qodo Cover to Qodo Gen) and the biggest numbers you’ll see quoted are typically vendor marketing claims rather than independently audited benchmarks. Evaluate any tool in this category against your own codebase’s coverage and mutation-testing results before trusting a headline percentage.
FAQ
Is Qodo Cover still usable?
The code may still run, but its GitHub repository has been explicitly marked unmaintained since June 2025, so it will not receive updates or fixes going forward.
Are Diffblue’s coverage claims independently verified?
Not as far as we could find. The 81% coverage and 2.5x/20x productivity figures come from Diffblue’s own press release, with no independent third-party benchmark replication located during this research.
Does AI-generated test coverage guarantee good tests?
No. Coverage percentage measures how much code is executed by tests, not whether those tests would actually catch a real regression — mutation testing or manual review is still the better way to judge test quality.
Sources
- Qodo Cover repository (github.com) — unmaintained notice
- Qodo Pricing (qodo.ai)
- Diffblue Testing Agent press release (BusinessWire) — vendor marketing claim
Discover more from Software Online Review
Subscribe to get the latest posts sent to your email.
