Covered - Reading the Report
Author: Trevor Williams

|  |  | 18
User Manual - «Covered»
|  |  | 12 Reading the Report
|  |  | This chapter describes the meanings of the textual report output that Covered generates when the report command is issued. It is well understood by the developers of Covered that a code coverage tool is only as good as the output that it generates, and this, of course, includes the ability to discern the information provided by the report. 24 | 25
|  |  | To help describe the various sections of a Covered report, we will use a relatively small Verilog file containing our DUT, generating the two main types of reports (module and instance) based on the CDD generated for this file. This example file is provided here.
|  |  | After being compiled and run, this module is scored with the following Covered command:
| Score Command |  | covered score -t main -v example.v -o example.cdd -vcd example.vcd
|  |  | The module-based verbose report can be viewed in its entirety here and is generated with the following command:
| Module-base report command |  | covered report -d v example.cdd
|  |  | The instance-based verbose report can be viewed in its entirety here and is generated with the following command:
| Instance-based report command |  | covered report -i -d v example.cdd
|  |  | The instructions for analyzing each of the four types of coverage information from the report can be found on the following pages.
|  |  | Reading Line Coverage Reading Toggle Coverage Reading Combinational Logic Coverage Reading FSM Coverage Reading Assertion Coverage
|  |  | For information on reading race condition information in the report, please see the user guide page detailing race conditions and viewing the reports.
|  |  | [ Contents | First Page | Previous Page | Home | Next Page | Last Page ] [ 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 ] License: GPL This Manual was created with ManStyle.