Coverage appears incorrect and code is not being matched to tests, per-test coverage

Still need help?

The Atlassian Community is here for you.

Ask the community

Symptoms

This will occur if

a) The tests have not been instrumented
b) All the tests have not been run

Look in your output for something like the following


clover Clover all over. Instrumented 146 files (25 packages).
clover 563 test methods detected.
...

clover-report Processed 1 test case result.
clover-report Processed 1 test case result from 1 results file.

Cause

The tests may not be instrumented if you have excluded them.
You also may not have run all the tests, and without running the tests. If the tests are not run, then the covereage will be incorrect and per-test coverage cannot work.

Resolution

Modify the build configuration or the command you are running to ensure that all tests are run

Last modified on Nov 21, 2012

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.