Clover-for-IDEA Glossary of Terms
Refers to common Java coding constructs or idioms such as the body of if statements; static initializer blocks; or property style methods. These are pre-defined by Clover.
The Cloverage view allows you to view and control Clover's instrumentation of your Java projects, and shows you the coverage statistics for each project based on recent test runs or application runs.
Coverage Cloud (report)
A Clover report visualization that prints class names to the screen, colored to show their level of code coverage and scaled in size to illustrate their complexity.
Coverage reports are generated by Clover as PDF, HTML or XML, showing Clover's output in a readily digestible format for the user.
Coverage Treemap (report)
A Clover report visualization that shows packages and classes as colored squares. The square's respective color indicates the level of code coverage and they are scaled in size to illustrate their complexity (largest is most complex).
Flush Policy (setting)
The Flush Policy controls when Clover writes coverage data to disk as your application runs.
This controls where the Clover plugin stores (and looks for) the coverage database.
In order to track the code coverage of your projects, Clover must insert special code into your programs at compilation time. This special code is collectively called instrumentation.
The Project view is a navigation side bar in IDEA that allows you to view the project tree and drill down into elements of the project structure visually, in order to select or edit them.
The Summary Panel is part of Cloverage view with a set of metrics that are displayed alongside the tree for the selected project, package, file, class or method in the tree.
Test Runs (view)
The Test Run Explorer view, like several popular plugins such as the JUnit Plugin or TestNG Plugin, lets you explore your recently run tests - showing whether they passed or failed, their duration and any error messages that they generated. Clover-for-IDEA takes this one step further and allows you to explore the code coverage caused by an individual test, a test class, a package or even your entire project.