
Balance your effort spent on writing application and test code.
Use the most sophisticated code coverage tool for Java and Groovy.
OpenClover measures code coverage for Java and Groovy and collects over 20 code metrics. It not only shows you untested areas of your application but also combines coverage and metrics to find the most risky code.
The Test Optimization feature tracks which test cases are related with each class of your application code. Thanks to this OpenClover can run tests relevant to changes made in your application code, significantly reducing test execution time.
Does testing getters and setters bring much value? Or machine-generated code? OpenClover outruns other tools in its flexibility to define scope of coverage measurement. You can exclude packages, files, classes, methods and even single statements. You can focus on testing important parts of your code.
OpenClover not only records test result but also measures individual code coverage for every test. It gives you deep insight on what your tests actually do. For a given test, you can find out which classes were executed during the test, down to a single line of code. Similarly, for a given class, you can see all tests related with it.
OpenClover has dedicated plugins for Jenkins and Bamboo. With a few clicks you can setup code coverage measurement for your builds. With OpenClover integrations with Ant, Maven and Grails you get even more flexibility.
OpenClover has plugins for IntelliJ IDEA and Eclipse. Thanks to them you can track your code coverage while coding and find untested areas before you commit your code to a repository.
We are thrilled to announce OpenClover 5.0. Support for Java 17, Groovy 5 and the latest Eclipse 2026 and IDEA 2026 makes a huge difference!
OpenClover has been free and open-source since 2017, and I intend to keep it that way. If you find OpenClover useful, even a single coffee goes a long way toward keeping the lights on.