3.28.4. Viewing the code coverage for a test run
Prev | 3.28. Working with code coverage with Java tests | Next

### 3.28.4. Viewing the code coverage for a test run

Once a test with code coverage has run, the code coverage information must first be processed in order to show it in the Test Result Summary View.

The following columns are available in the Test Result Summary View to show you code coverage information:

| If a column is not visible, you can show it by selecting it from the context-sensitive menu on the header row for the Test Result Summary View.

- The Profiling Agent column displays which code coverage agent was selected for the test run.

- The Measured Value column shows the Instruction Coverage for the test run. You can see the values for other types of coverage in the Properties View when you select the test run. An overview of the meanings of the coverage types is available on the JaCoCo website:

  http://www.eclemma.org/jacoco/trunk/doc/counters.html.

  | The measured value will become visible once the code coverage information has been processed. You may need to refresh the Test Result Summary View.

- The Profiling Details column indicates whether the full details for the code coverage report are still in the database. Full profiling details are removed from the database at the same time as test run details (Section 3.22.3.1, “Re-opening the test result view for a test run”). The period of time that details remain in the database can be specified in the Project properties (Section 3.6.3.1, “Editing general Project properties”).

Opening and viewing the code coverage report

1. In the Test Result Summary View, select the test run whose code coverage you want to see and click the ”Open Profiling Report” button at the top of the view.

   | The details about code coverage are available in the database for the same amount of time as the test result details (Section 3.22.3.1, “Re-opening the test result view for a test run”). After this time, the code coverage details are deleted along with the test run details.

2. In the editor that opens, you can see the details for the code coverage for the test run.

3. If you specified a source file directory for your AUT (Section 3.28.2, “Configuring code coverage for an AUT”) and compiled your AUT classes with debug information, you will be able to navigate through your classes to see more detailed information about the code coverage through the whole AUT.

4. Once you have opened a code coverage report, it is saved into your workspace. You can reopen it from the Navigation View.

   | You should regularly remove old code coverage reports from your workspace to avoid overfilling it.