Code Coverage Analysis Is The Process of
Code Coverage Analysis Is The Process of
Cntnd
You use coverage analysis to assure quality of
your set of tests, not the quality of the actual
product.
You do not generally use a coverage analyzer
when running your set of tests through your
release candidate.
Coverage analysis requires access to test
program source code and often requires
recompiling it with a special command.
What is Covered?
Covered is a Verilog code coverage analysis tool that can be useful for
determining how well a diagnostic test suite is covering the design
under test (DUT). It is command-line based with an optional Tcl/Tk GUI
report viewer, making it portable across almost all platforms.
Covered is a tool that uses your design files along with standard VCD,
LXT2 or FST dump files to analyze the code coverage of the DUT. The
code coverage information is stored in a special database file that can
be retrieved and "merged" with new coverage information to create a
summed coverage total for several tests.
After a database file has been created, the user may generate various
ASCII reports that summarize the coverage information or run
Covered's GUI to interactively analyze the coverage information.
Additionally, multiple CDD files from the same design can be ranked
for the purposes of running regressions and understanding which CDD
files do not add coverage information and can be excluded from
regressions runs, if needed.
Cntnd
Covered currently supports Verilog-1995, Verilog2001 (with the exception of config blocks
currently), and SystemVerilog constructs. Metrics
that are generated include the following:
Line coverage
Toggle coverage
Memory coverage
Combinational logic coverage
FSM state and state-transition coverage
Assertion (functional) coverage