Dashboards | Diffblue Documentation

Home page - list view: Click the Cover Reports logo (or the Home icon in the project path) to view your project list. Click a line item (project, sub-project, package, etc) to view the coverage data. Click the Delete icon to delete a project and all associated data (runs). Click the Overview and Map tabs from the home page to view data for your entire set of projects.
Menu - structure view: As you'd expect, your projects are organised and displayed in a standard tree structure and you can navigate through your projects, sub-projects, packages, classes, and methods as needed. The coverage data visible from the dashboards reflects the current selected component.
Dashboards - data view: Three main dashboards/tabs are available for data visualization (Overview, Map, and Coverage Detail). The Overview and Map tabs are available from the home page, and all three tabs are available as you navigate down into the structure of your individual projects.
Runs - versions: As you create and upload coverage data over time, use the Latest Run drop-down to select what data to view. Click the Delete icon for a run to delete the individual run and associated data.
Search: Use the search to find a project, package, or class across all of your projects.

Your project names are automatically calculated based on the Java project configuration. Report bundles are uploaded to a default Projects folder.

Overview Tab - an overview/summary of coverage data for your project/project component. Here's a quick breakdown of the panels and the terminology used for the data.

Project Overview - the four key data stats.
- Diffblue Coverage - coverage (percentage) provided by all Diffblue Cover Tests.
- Total Coverage - total coverage (percentage) provided by Diffblue Cover Tests and/or Manual Tests (existing developer written tests).
- Lines of Code - total lines of code for the selected project component.
- Number of Tests - total number of tests created by Diffblue Cover.
Coverage Sources & Coverage Over Time - a more detailed breakdown.
- By Diffblue tests only - percentage / LOC (Lines of Code) covered exclusively by Diffblue Cover Tests only.
- By manual tests only - percentage / LOC (Lines of Code) covered exclusively by Manual Tests only (existing developer written tests).
- By Diffblue and manual tests - percentage / LOC (Lines of Code) covered by Diffblue Cover Tests and Manual Tests (existing developer written tests) - i.e. this is the overlap of the two types of test.
- Trivial, Untestable, Not tested - percentage / LOC (Lines of Code) that Diffblue Cover was unable to write tests for. In many cases this is due to issues such as private methods, empty methods, trivial setters and getters, etc. You can use the Coverage Detail tab to get more detailed information (output codes) but that's a topic for later - see Output Codes.
- Excluded - percentage / LOC (Lines of Code) which do not have coverage and were excluded (by the user) from Diffblue Cover test creation.
- Unknown - percentage / LOC (Lines of Code) where the testability could not be determined by Diffblue Cover.

Map Tab - a coverage heat map for your project/project component.

Click an item to drill down further through your project structure.
Use the toggles to change coloring and sizing option.

Coverage Detail Tab - a detailed coverage breakdown. Here's a quick breakdown of the panels and the terminology used for the data.

Total Output codes - total number of output codes (see note below) generated by this run of Diffblue Cover.
Total Not covered lines - total lines of code not covered by any tests.
Stats list table - a full breakdown for each project component:
- Lines of Code - total lines of source code.
- Not Covered Lines - total lines of source code that are not covered by any tests.
- Diffblue Coverage - percentage coverage provided by all Diffblue Cover Tests.
- Total Coverage - total coverage (percentage) provided by Diffblue Cover Tests and/or Manual Tests (existing developer written tests).
- Manual Coverage - percentage coverage provided by all Manual Tests (existing developer written tests).
- Diffblue Test Count - total number of Diffblue Cover Tests.
- Advisories - output code details (see note below).

Note - Output Codes - Diffblue Cover performs a number of checks before, during, and after creating unit tests. Cover can generate a range of output codes during these checks to provide general information and highlight any potential issues. See Output Codes for more details.