Coverage.py
7.3#3 in test coverage toolsFree planFree planAPILinuxmacOSSelf-hosted
VisitCoverage.py vs OpenClover
OpenClover
6.4#10 in test coverage toolsFree planFree planWebLinuxmacOSWindows
VisitWhat both publish
| Fact | Coverage.py | OpenClover |
|---|---|---|
| Coverage types | It measures statement coverage by default and can also measure branch coverage. | It tracks global, per-test and distributed per-test coverage with method, statement and branch metrics. |
| Integrations | Official examples cover pytest, unittest, and nose, and pytest commonly uses the pytest-cov plugin. | Integrations include Ant, Maven, Gradle, Grails, Griffon, Jenkins, Bamboo, Eclipse, IntelliJ IDEA, Sonar and JIRA. |
| License | Coverage.py is licensed under the Apache 2.0 License. | OpenClover software is licensed under Apache 2.0. |
| Purpose | Coverage.py measures which parts of Python programs ran and identifies executable code that did not run, commonly to gauge test effectiveness. | OpenClover is a code coverage tool for Java, Groovy and AspectJ. |
| Report formats | Reports can be emitted as text, HTML, XML, LCOV, or JSON. | Reports can be generated as HTML, XML, PDF, JSON and TEXT. |
Coverage.py plans
- Coverage.pyFree
- FreeFree
OpenClover plans
- OpenCloverFree
Pick Coverage.py if…
Coverage.py is for developers measuring how much of their Python code their tests exercise. Its report formats and dynamic contexts can help teams inspect coverage in different ways.
Pick OpenClover if…
OpenClover suits developers working with Java, Groovy, or AspectJ who want coverage metrics and test rerun selection. Teams using its Eclipse or IntelliJ IDEA integrations should note that Groovy is not supported there.