Clover

Features Eclipse Plugin

Instrument your code and view coverage statistics from within the Eclipse IDE.

Toolbar

A perfect match

Clover integrates seamlessly with the Eclipse IDE, bringing code coverage analysis to your Eclipse workbench. Together, Clover and Eclipse provide an interactive development desktop that allows you to record and browse source-level coverage without leaving the IDE.

Clover-Eclipse integration

The 'Coverage Explorer'

The Coverage Explorer viewer is automatically added to the Eclipse workbench when you enable Clover for your project:

Clover Coverage Explorer

The tree shows the project, package and class coverage and complexity information for all Clover-enabled projects. Summary statistics are displayed alongside the tree for the selected project/package/class.

The convenient popup menu provides coverage viewing and recording options all in one place:

Clover Coverage Explorer menu

The 'Test Run Explorer'

After running tests in a Clover-enabled project, this is easily displayed by selecting the Test Run Explorer view.

Twin panels show all recently run tests, whether they passed or failed, and any errors they generated, cross-referenced against the code coverage that belongs to each one:

Clover Test Run Explorer

This gives you piercing insight into the depth to which your application class was tested, and the amount of coverage each test was responsible for. In turn, this information allows you to write far more focused follow-on tests, for improving your code coverage.

View it your way

There are five ways to view your Clover code coverage data within Eclipse:

  • As a marker in the Eclipse 'Overview' bar (right-hand side). This marker has a tooltip indicating the coverage problem.
  • As a coloured annotation of the source code in the Java editor.
  • As a tag cloud report highlighting the classes that form major project risks (low coverage, high complexity) and potential quick wins for increasing project coverage.
  • As a treemap report allowing simultaneous comparison of classes and package by complexity and by code coverage. Double click on any class to open the corresponding source file in an editor.
  • By reporting on the unit tests and methods that generated coverage for the currently opened Java source file:

Clover Coverage treemap report

Tell me more

Please see the Clover Eclipse Plugin documentation.

Features home page