Checking code coverage

Well, only writing unit tests is not enough – you still need to know how muchof the code your tests test. This is why a code coverage tool is great.

Clover is one of the tols used to compute code coverage and is now updating to a 2.0. The beta is on the site and it seems to add some interesting features:

  • dril down in the test suite to see what statements each code provides
  • Per-method coverage statistics
  • Complexity statistics
  • Simplified Ant Tasks
  • Integrated historical reporting
  • Aggregate package statistics
  • Configurable report columns, column formats and column thresholds
  • Improved runtime coverage recording performance
  • New runtime configuration options to control coverage recording

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s