Clover

Features Continuous Automation

Add coverage reporting to your automated build process.

Use Clover in your automated builds

Clover's coverage measurement can be easily integrated into your automated build process, generating coverage reports on a regular basis. Clover works with all popular build servers.

Clover-Bamboo integration

Note that many developers also augment this automated process by using Clover interactively in their day-to-day coding.

Generate reports for your team

Clover can write coverage reports to your chosen location, in your chosen format.

Usage example: The latest test coverage results are written to the intranet each week as an HTML report. Additionally, a summary PDF report is emailed to the project manager for inclusion in the weekly project status report.

Track coverage over time

By automating Clover, you can collect coverage metrics each time your tests are run. This enables you to build up data for generating historical reports, so you can track your project's progress over time.

Coverage over time

Coverage goals ('quality thresholds')

Criteria checking and triggers

As part of the automation process, you can use the Clover Ant tasks to monitor coverage criteria. If coverage does not meet your chosen criteria, you can configure how Clover will react.

Usage example: If project coverage is not 80%, the project build is failed.

Features home page