Clover
Features – Test Insight
Whatever your testing regime, Clover provides intelligent insight into the results.
Test results integrated with coverage results
Clover's reports fully integrate the results of your latest test run. Not only can you see source-level coverage, but you can also see for each statement:
- which tests contributed what coverage
- the results of each test (pass/fail; time taken)
- any error messages
- hyperlinked stack traces for failed tests
Browse the test results for each package and drill down to see results for test suites and individual test case runs.
Detailed per test reporting
Clover takes coverage analysis to a new level by not just showing you what code is covered by your tests, but also which tests hit what code.
Developers can quickly gain insight into how much each of their tests contributes to the project's coverage. This allows them to spot any testing weaknesses or redundancies, and verify that each test is actually testing the code it was intended to exercise.
Drill down to a particular class to see the exact statements a particular test or set of tests covered. For each test case, you can jump straight to the source code for that test. If the test failed, Clover will link to the source line where the failure occurred.
Regime agnostic
Whether your focus is on system tests, functional tests, or unit tests, Clover provides intelligent insight into the results.
Clover doesn't just give you raw coverage data: it helps you make practical use of it. Clover automatically 'rates' the coverage, so that you can see:
- Was the code deliberately covered by a test, or was it just covered incidentally?
- Was the code covered by just one test, or by many tests?
- Which parts of your code pose the highest risk to your project — i.e. which code is most complex and least tested?
