This page contains definitions of terms used in the Clover-for-Eclipse plugin documentation.
On this page:
Avg Method Cmp
The average method complexity of code in the given context.
Refers to common Java coding constructs or idioms such as the body of if statements; static initialiser blocks; or property style methods. These are pre-defined by Clover.
Clover Working Set
A specified set of files, directories and projects that Clover will report on. Especially useful when working with large projects.
Cyclomatic coMPlexity of code in the given context.
The complexity density of code in the given context.
Individual data sources that comprise part of a chart, visualisation or report.
Coverage Explorer (view)
The Coverage Explorer 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 Explorer Column Chooser
A configuration screen that allows the user to set what is displayed in the Coverage Explorer, by selecting from the 24 columns available in Clover. The Column Chooser can be summoned by selecting "Columns..." in the Coverage Explorer view menu.
Coverage Explorer Custom Column Builder
A dialog that allows the user to define custom columns that show computed values from the data points used in Clover's reporting framework.
Coverage Cloud (report)
A Clover report visualisation that prints class names to the screen, coloured 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. These reports can be generated for single or multiple projects.
Coverage Treemap (report)
A Clover report visualisation that shows packages and classes as coloured squares. The square's respective colour 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.
Lines Of Code (including comment lines).
Non-Commented Lines Of Code. Lines of code that contain comments are not counted in this metric, leaving only the actual functioning code itself.
Perspective (Eclipse concept)
In the Eclipse IDE, each window in the desktop development environment contains one or more perspectives. Perspectives are containers for views and editors which control the content of the navigation user interface and controls.
Project Explorer (view)
In Eclipse, the Project Explorer view shows a hierarchical view of the resources in the Workbench.
The Summary Panel is a set of metrics that are displayed alongside the tree for the selected project, package, file, class or method in the tree.
Test Contributions (view)
The Test Contributions view shows unit tests and methods that generated coverage for the currently opened and selected Java source file.
Test Run Explorer (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-Eclipse 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.
Workspace (Eclipse setting)
The 'General > Workspace' page is a configuration screen that is used to access IDE preferences in Eclipse.
Workbench (Eclipse concept)
A general term for the Eclipse desktop development environment.