Knowledge Base > Diffblue Cover Reports 2.0 > 6. Using Tables in Cover Reports

Using Tables in Cover Reports

BETA

Cover Reports has many tables that explain the data behind a coverage report returned after running dcover create. This page aims to explain those tables in detail.

Coverage Summary

This table breaks down how the code is tested (or not tested) and displays the amount of lines covered by each test method.

There are several types of this table, which show coverage at different levels within the project:

  • Run coverage: presents the lines covered in the module
  • Package Coverage Summary: presents the lines covered in the package
  • Class Coverage Summary: presents the lines covered in the class

In the package and class summaries, this table will also include the number of tests created by Diffblue as well as the number of output codes found.

Below are examples of this table - first from the Run Summary, then the Class Summary dashboard.

Packages List per run

This table shows all packages in the project for the run and provides a link, so that the user can navigate to the package summary dashboard for each package.

Here is an example:

Classes in package

The classes in package table breaks down the lines of code found within the classes of the chosen package, and displays the percentage of those lines of code that are covered by:

  • Manual tests
  • Diffblue tests
  • Both

This table also displays the amount of Diffblue tests created for each class and the amount of problems found within those classes represented by output codes.

Below is an example of this table:

Methods in class

The methods in class table works much the same as the classes in package table, but instead it expands into each of the methods within the class. Output codes are not found on this table.

Coverage by all methods - a pivot table

The pivot table shows the same information as the classes in package and method in class tables. However, the pivot table allows the user to see exactly the information that they are interested in.

By default, the pivot table shows all coverage types across the whole module. There are seperate rows within the table for the different packages and classes that make up the module.

The pivot table also only includes raw information (i.e the number of lines tested) as opposed to any calculated data (i.e percentage of coverage).

Below is an example of what this looks like:

Users can also change the value of the dropdowns however to suit the information that they are specifically looking for.

For example, a user could choose to see only a specific class within a module and they could also deselect certain coverage types to remove them from the table.

Below is an example of what this looks like:

Whole Run Summary

This table seeks also to show the overview of the coverage of a project.

It breaks the module down into classes and methods, in a heirarchical view, and displays the amount of code contained within - as well as how the code is covered by Diffblue and manual testing.

The lines of code shown for the class is equal to the sum of its classes, which are broken down and displayed beneath it.

The table will then show the percentage of those lines of code that are covered by manual tests, Diffblue tests and all tests combined.

The user can also order the table by any of the table headers should they wish.

Below is an example of what this table looks like:

Output codes

When DCover runs, if there is a problem with a method that hinders test creation, an output code is provided. To see which methods have produced output codes, this table can be used.

There are several types of this table:

  • Output codes for the run
  • Output codes for the package
  • Output codes for the class

Here is an example of a table showing the output codes for a run:

There is a list of all output codes in the top left. This can be used to filter the results for a particular code. In the example shown the filter is set to show only R002