Java code coverage tools
 | This article or section is in a state of significant expansion or restructuring. You are welcome to assist in its construction by editing it as well. If this article or section has not been edited in several days, please remove this template. If you are the editor who added this template and you are actively editing, please be sure to replace this template with {{in use}} during the active editing session. Click on the link for template parameters to use.
This article was last edited by ThurnerRupert (talk | contribs) 12 years ago. (Update timer) |
| Developer(s) | Marc Hoffmann, Brock Janiczak, Evgeny Mandrikov |
|---|---|
| Stable release | 0.6.2
/ February 3, 2013 |
| Operating system | Cross-platform |
| Type | Code coverage |
| License | EPL |
| Website | EclEmma JaCoCo |
Clover is a Java Code Coverage Analysis application developed by Atlassian. Although Clover is a commercial product, it is freely available to open source projects and non-profit institutions.
Some features include historical reporting, complete control over the coverage gathering process, command line toolset and API for legacy integration and more.
Clover also allows testing time to be reduced by only running the tests that cover the application code that was modified since the previous build. This is called Test Optimization and can lead to huge drops in the amount of time spent waiting for automated tests to complete.
A clover invocation from Apache Ant might look like:
<target name="html-clover-report" depends="define-tasks">
<mkdir dir="${core.dir}/output/clover/html" />
<clover-html-report outdir="${core.dir}/output/clover/html" title="aTAO Project"/>
</target>
where "define-tasks" would include:
<taskdef resource="cloverlib.xml" classpath="${clover.jar}"/>
See also
External links
- JaCoCo vs Clover2
- Pick your code coverage tool in Sonar 2.2, a little outdated, as JaCoCo meanwhile supports branch coverage.
 | This programming-tool-related article is a stub. You can help Wikipedia by expanding it. |