Using tables in Cover Reports
Describes the various tables in Cover Reports
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.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.
Run Summary
Class Summary
This table seeks also to show the overview of the coverage of a project, package or class.
It breaks the module down into classes and methods, in a hierarchical 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 methods, 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.
When viewing a project group, this table will display all classes and methods within each of the projects aggregated by the group.
Below is an example of what the Coverage Details table looks like:
When
Cover runs, if there is a problem with a method that hinders test creation, an output code is provided. To see which areas of your code have produced output codes, the Coverage Details table can be used.The output codes
Cover produced for each method are in the right-most column of the table. Each code will have a brief description next to it. The output code itself can also be clicked. Doing so will take you to our Output Codes, where the user can see more information about the output code.Classes will be fully qualified, but may be truncated if they are too large. When hovering over the truncated class name, the fully qualified name of the class will be displayed in a popup.
The methods of each class will be initially hidden from view. When the user clicks on the class, it will expand to show details for each method in that class.
When there are more than 25 classes in the project or package, they will be split, so at most only 25 classes will be seen in the table at once. To view other classes, the user can use the page controls directly beneath the table.
The user can also order the table by any of the table headers should they wish.
Last modified 20d ago