Knowledge Base > Diffblue Cover Reports > 5. Dashboards
Cover Reports Dashboards
Cover Reports has many dashboards that help to provide overviews of a coverage report returned after running dcover create. This page aims to clarify those dashboards and their contents.
Run
Overview
This dashboard represents a top-down overview of the project for a run. It aims to display total package coverage, where that coverage comes from, and outlines the packages within the module tested.
The run can be selected using the select list in the top right.
There are several widgets providing data to this dashboard. They will show data for the chosen run.
Status Widgets
In the top left of the dashboards, the first widgets relate to the overall status of the run. These include:
- Diffblue coverage
- The percentage of a project’s code covered by Diffblue tests alone.
- Total coverage
- The percentage of a project’s code covered by Diffblue and manual tests combined.
- Diffblue tests
- The amount of tests Diffblue has generated for the project
- Risk Index
- The risk (out of 100) that incomplete testing has to the project
Tables
There are several tables shown:
Visualisations
There is a visualisation shown:
Coverage Reports
This dashboard contains a series of visualisations that show coverage for the whole run:
- Where are the uncovered lines?
- How many lines are covered?
- Coverage by all methods - a pivot table
- Coverage optimization
Coverage Details
This dashboard contains a table with coverage information for the whole run.
This information is broken down into Classes and then further into methods, with information regarding percentage of code covered and total test count for each method.
See whole run summary for more on this table.
Output Codes
This dashboard helps find problems in the project that can be solved to help improve coverage. It shows:
Map
This dashboard shows an overview of the entire project:
Package
Overview
The package summary dashboard aims to break down a specific package within your project.
This dashboard allows you to view the breakdown of each class within the package and how well the class is covered.
These can be seen using the Coverage Summary table, which breaks down the total lines of code within the package by how the code is covered.
Coverage Reports
This dashboard contains a visualisation that shows coverage for the package:
Coverage Details
This dashboard contains a table with coverage information for the package:
It breaks down the lines of code tested in each class by test types, and how much coverage each test type provides. This is represented as a percentage of the lines of code in the package.
Output Codes
This dashboard helps find problems in the package that can be solved to help improve coverage. It shows:
Class
Overview
The class summary dashboard aims to break down a specific class within your project.
This dashboard allows you to view the breakdown of each contained method and how well the methods are covered.
These can be seen using the Coverage Summary table, which breaks down the total lines of code within the class by how the code is covered.
Coverage Reports
This dashboard contains a visualisation that shows coverage for the class:
Coverage Details
This dashboard contains a table with coverage information for the class:
It breaks down the lines of code tested in each method by test types, and how much coverage each test type provides. This is represented as a percentage of the lines of code in the class.
Output Codes
This dashboard helps find problems in the class that can be solved to help improve coverage. It shows:
Output codes with uncovered lines for the class
Telemetry
The telemetry dashboards are accessed in a different way to the other dashboards, as you need to enter a URL. They also require you to have set up telemetry. Both the CLI and the plugin telemetry dashboards show information about your users:
- Total unique users per day
- Total number of write test operations per day
- Total tests produced per day.