Java and Groovy code coverage

Clover provides the metrics you need to better balance the effort between writing code that does stuff, and code that tests stuff.

Clover runs in your IDE or your continuous integration system, and includes test optimization to make your test run faster, and fail more quickly.

 
 
Clover Logo

Pricing overview

1 machine

Desktop $300

1 machine

Server $1,200

10 machines

Desktop or Server $2,200

25 machines

Desktop or Server $4,000

100 machines

Desktop or Server $8,000

100+ machines

Desktop or Server $16,000
View full pricing details»

Clover + Bamboo

Clover integrates with your Atlassian Bamboo continuous integration server to display test coverage metrics in your build results.

  • Coverage trends across builds indicate when new risks are introduced.
  • Test optimization speeds your builds by only running tests that cover changed code or that previously failed.

Ant, Maven, and more

Clover can integrate with almost any build system, including those based on:

  • Ant
  • Maven 1 & 2
  • Jenkins
  • Command line tools

Jenkins integration

Capture Clover code coverage information in the Jenkins continuous integration build server at the click of a button. Identify project risks and observe coverage and code metric trends over time with Clover integration.

  • Coverage results in Jenkins builds
  • Clover code coverage in Jenkins weather report

Clover customers

Over 600 companies in 47 countries use Clover. Meet our customers.

Latest Clover blog

Marek Parfianowicz

Clover 3.3 is a great choice for Spock tests

The Spock Framework is one of the best unit testing frameworks compatible with JUnit. It’s based on the Groovy language and it takes its capabilities to an upper level (thanks to huge AST trans ...

Read more on the Clover Blog