Clover Concepts & Usage FAQ
- Can I create a Clover Report on Server A if I have the clover.db which I generated on Server B?
- Does Clover depend on JUnit? — Clover has no dependence on JUnit. We mention it frequently in our documentation only because of JUnit's widespread use in the Java development community.
- Does Clover integrate with Maven? — There is a Clover Plugin for Maven and Maven2 — both are independent open source developments supported by Cenqua/Atlassian.
- Does Clover support the new language features in JDK1.5? — Clover fully supports all JDK1.5 language features.
- Does Clover work with JUnit4 and TestNG? — Clover is fully compatible with JUnit4 and TestNG.
- How are the Clover coverage percentages calculated? — The "total" coverage percentage of a class (or file, package, project) is provided as a quick guide to how well the class is covered — and to allow ranking of classes.
- How do I compare the code coverage between two releases of my code?
- How do I get started with Clover? — See the Clover-for-Ant QuickStart Guide
- How do I use Clover with NetBeans?
- What are the limitations of Code Coverage? — Code Coverage is not a "silver bullet" of software quality, and 100% coverage is no guarantee of a bug-free application. You can infer a certain level of quality in your tests based on their coverage, but you still need to be writing meaningful tests.
- What does the name "Clover" mean? — Clover is actually a shortened version of the tool's original name, "Cover Lover", from the nick name that the tool's author gained while writing Clover ("Mr Cover Lover").
- What is Code Coverage Analysis? — Code Coverage Analysis is the process of discovering code within a program that is not being exercised by test cases.
- What is the coverage.db file and why am I seeing files like coverage.dbxxxxxxxxx_xxxxx_xxxx? — The coverage.db file is the instrumentation database telling Clover the structure of your project and files during the last instrumentation event. coverage.dbxxxxxxxxx_xxxxx_xxxx hold the code coverage from your unit test or application run.
- What third-party libraries does Clover utilise?
- Where did Clover originally come from? — Clover was originally developed at Cenqua (now part of Atlassian) as an internal tool to support development of large J2EE applications.
- Why does Clover instrument classes I have excluded using the 'exclude' element of the 'clover-setup ' task? — There are two possible causes:
- Why does Clover use Source Code Instrumentation? — Source code instrumentation is the most powerful, flexible and accurate way to provide code coverage analysis.
- Will Clover integrate with my IDE? — Clover 2 provides an integrated plugin for Eclipse, with more plugins soon to follow.
Overview
Content Tools
Apps
Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.