OpenClover
openclover.org
- Free plan
- Windows
- macOS
- Linux
- Web
What OpenClover is
OpenClover is a free, open-source code coverage tool for Java, Groovy, and AspectJ. It measures coverage globally, for individual tests, and across distributed tests, using method, statement, and branch metrics. The tool includes more than 20 built-in code metrics and also supports custom metrics. Reports can be generated in HTML, XML, PDF, JSON, and text formats. Coverage can be filtered by paths, classes, methods, code blocks, statements, complexity, and inline comments. For test optimization, OpenClover can identify tests to rerun when classes change, run failing tests first, or randomize test order. Integrations include Ant, Maven, Gradle, Grails, Griffon, Jenkins, Bamboo, Eclipse, IntelliJ IDEA, Sonar, and JIRA. Dedicated test support covers JUnit 3 and 4, TestNG, and Spock. Version 5.1.x supports JRE or JDK 8 through 25 and Groovy 3.x, 4.x, and 5.x. Groovy is not supported in its Eclipse and IntelliJ IDEA integrations. The project is Apache 2.0 licensed and community support typically responds within a few days.
Who it suits
OpenClover suits developers working with Java, Groovy, or AspectJ who want coverage metrics and reports as part of their testing workflow. It may also suit teams using its listed build, CI, IDE, or issue-tracking integrations.
Good to know, and what to watch
- Tracks method, statement, and branch coverage.
- Includes over 20 built-in code metrics.
- Reports are available in five formats.
- Can identify tests to rerun for modified classes.
- Free with no license tiers, keys, or usage limits.
- Groovy is unsupported in Eclipse and IntelliJ IDEA integrations.
- Community support typically responds within a few days.
Plans
Every plan and priceOpenClover
Free plan
Getting started
- Open the OpenClover website
- Use the free OpenClover software under Apache 2.0
- Integrate it with Ant, Maven, Gradle, Grails, Griffon, Jenkins, Bamboo, Eclipse, IntelliJ IDEA, Sonar, or JIRA
- Connect a supported test framework such as JUnit, TestNG, or Spock
- Configure coverage filters and choose an HTML, XML, PDF, JSON, or text report
Limits to check
OpenClover has no license tiers, license keys, or usage limits. Groovy support is unavailable in its Eclipse and IntelliJ IDEA integrations.
The Club's review
Overview
OpenClover is a free, Apache 2.0-licensed code-coverage tool for Java, Groovy and AspectJ. It suits development teams that want detailed coverage analysis tied to builds, tests and continuous integration rather than a minimal one-click report.
Its strongest case is breadth: global, per-test and distributed per-test views, multiple code metrics, historical trends, coverage gates and test-selection features are included without licensing or usage limits. The trade-off is that Groovy is not supported in its Eclipse or IntelliJ IDEA integrations.
For other options, see our Test Coverage Tools directory.
Key features
Coverage and code analysis
OpenClover measures method, statement and branch coverage globally, per test and across distributed tests. That gives teams more useful diagnostics than a single project-wide percentage, especially when a change affects only part of a suite. Historical trends help track movement over time, and coverage gates provide a basis for enforcing thresholds.
More than 20 built-in code metrics, plus custom metrics, extend the tool beyond test execution. Filters can narrow analysis by path, class, method, code block, statement, complexity or inline comment. This is valuable for large codebases, although teams seeking only a lightweight coverage summary may find the scope broader than necessary.
Build, test and reporting workflow
Ant, Maven, Gradle, Grails and Griffon integrations fit common Java and Groovy build pipelines. Jenkins, Bamboo, Sonar and JIRA connections support continuous integration and issue-oriented workflows. Dedicated support for JUnit 3 and 4, TestNG and Spock covers established test stacks.
Reports can be exported as HTML, XML, PDF, JSON or TEXT, so results can serve people, automation and archival processes. OpenClover can identify tests to rerun after classes change, run failing tests first, or randomize test order. These options can reduce feedback time or expose order-dependent tests, provided the surrounding build is configured to use them.
Runtime and support
OpenClover 5.1.x supports JRE or JDK 8 through 25 and Groovy 3.x, 4.x and 5.x. It runs on Microsoft Windows, Linux and Apple Mac OS X, with a web reporting experience. Community support through documentation, forums and the issue tracker typically responds within a few days. Volunteer maintenance has kept the project free and open-source since 2017.
Pricing
OpenClover costs nothing, billed forever. There are no license tiers, license keys or usage limits, making it suitable for individuals, teams and organizations that need unrestricted coverage collection without a commercial subscription.
The free plan gives up nothing through seat quotas or metered usage, but support is community-based rather than a paid service commitment. Organizations that require guaranteed vendor response may prefer a commercial alternative.
Platforms
OpenClover supports Linux, macOS, Windows and web access. Its runtime covers JRE or JDK 8–25. Java and AspectJ integrations are broad, while Groovy projects should account for the lack of Groovy support in the Eclipse and IntelliJ IDEA integrations.
Who it's for
Choose OpenClover for Java, Groovy or AspectJ teams that need detailed per-test coverage, configurable metrics, coverage gates and integration with established build or CI tooling. It is particularly well suited to organizations that want historical analysis and test-impact selection without licensing costs.
It is less suitable when IDE-based Groovy coverage in Eclipse or IntelliJ IDEA is essential, or when you want commercial support with a formal service guarantee.
Pros and cons
Pros
- Unrestricted free plan: no license keys, tiers or usage limits.
- Deep coverage detail: global, per-test and distributed views with method, statement and branch metrics.
- Broad automation fit: Ant, Maven, Gradle, Jenkins, Bamboo, Sonar, JIRA and several test frameworks are supported.
- Flexible analysis: 20-plus built-in metrics, custom metrics and granular filtering.
- Useful test optimization: changed-class test selection, failing-tests-first execution and randomized ordering.
Cons
- Groovy IDE gap: Groovy is unsupported in the Eclipse and IntelliJ IDEA integrations.
- Community-only assistance: typical responses take a few days and do not provide a commercial support commitment.
- Broad configuration surface: extensive metrics and filters may be unnecessary for teams wanting a simple report.
Alternatives
Coveralls is a better fit for hosted coverage workflows, with a freemium model and an always-free offering for open-source and public repositories.
ReportGenerator suits users who want a free basic open-source tier, a 10-day full-access trial or paid individual features across desktop platforms.
BullseyeCoverage is worth considering when a paid product and fully functional temporary evaluation license are preferable.
Codecov fits hosted API, web or self-hosted workflows, with a free Developer plan whose limits differ for public and private repositories.
cargo-llvm-cov is the simpler choice for Rust projects using an Apache-2.0 or MIT-licensed free tool.
Coverage.py is the natural alternative for Python coverage, with an open-source tool and optional enterprise access through Tidelift.
Microsoft Code Coverage is a free, closed-source option for supported Windows, Linux and macOS workflows.
EclEmma is preferable when an Eclipse plug-in focused on Java coverage is all you need.
Verdict
OpenClover is a strong recommendation for Java, Groovy and AspectJ teams that want unusually comprehensive coverage views, metrics and test-optimization controls at no cost. Look elsewhere if Groovy coverage inside Eclipse or IntelliJ IDEA, or guaranteed commercial support, is a central requirement.
The verdict
OpenClover combines several coverage views with test-selection tools and a broad set of integrations. Check IDE support if your work depends on Groovy in Eclipse or IntelliJ IDEA.
Questions people ask
How much does OpenClover cost?
OpenClover is free forever at no cost, with no license tiers or keys.
Which languages does it cover?
It supports Java, Groovy, and AspectJ.
Which test frameworks are supported?
Dedicated support covers JUnit 3 and 4, TestNG, and Spock.
What report formats are available?
Reports can be generated as HTML, XML, PDF, JSON, and TEXT.
Which operating systems and runtimes are supported?
It supports Windows, Linux, and macOS. OpenClover 5.1.x supports JRE or JDK 8 through 25 and Groovy 3.x, 4.x, and 5.x.
Is OpenClover open source?
Yes. It has been free and open-source since 2017 and is licensed under Apache 2.0.
What the maker publishes
- Code metrics
- It includes over 20 built-in code metrics and supports custom metrics. source
- Coverage types
- It tracks global, per-test and distributed per-test coverage with method, statement and branch metrics. source
- Data filtering
- Coverage scope can be filtered by paths, classes, methods, code blocks, statements, complexity and inline comments. source
- Founded
- 2017 source
- IDE limitation
- Groovy is not supported in the Eclipse and IntelliJ IDEA integrations. source
- Integrations
- Integrations include Ant, Maven, Gradle, Grails, Griffon, Jenkins, Bamboo, Eclipse, IntelliJ IDEA, Sonar and JIRA. source
- License
- OpenClover software is licensed under Apache 2.0. source
- Project status
- OpenClover is maintained by volunteers and has been free and open-source since 2017. source
- Purpose
- OpenClover is a code coverage tool for Java, Groovy and AspectJ. source
- Report formats
- Reports can be generated as HTML, XML, PDF, JSON and TEXT. source
- Runtime support
- OpenClover 5.1.x supports JRE or JDK 8 through 25 and Groovy 3.x, 4.x and 5.x. source
- Supported operating systems
- Supported operating systems are Microsoft Windows, Linux and Apple Mac OS X. source
- Technical support
- Community support typically responds within a few days through documentation, forums and the issue tracker. source
- Test frameworks
- Dedicated test support covers JUnit 3 and 4, TestNG and Spock. source
- Test optimization
- It identifies tests to rerun for modified classes and can run failing tests first or randomize test order. source
Checked against the maker's pages on 1 Oct 2026.