diff options
author | dmcmahill <dmcmahill@pkgsrc.org> | 2003-08-24 18:38:06 +0000 |
---|---|---|
committer | dmcmahill <dmcmahill@pkgsrc.org> | 2003-08-24 18:38:06 +0000 |
commit | bab39f4634f1e50801969f9089b37ad2ab17dd6e (patch) | |
tree | 3ac898a638403508d1a225c7dab165008965824e /print/teTeX2-bin/PLIST | |
parent | 7c4fc6c25827af1c420f65265368056683f30854 (diff) | |
download | pkgsrc-bab39f4634f1e50801969f9089b37ad2ab17dd6e.tar.gz |
import covered-0.2.1
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. Typically in the design verification work flow, a
design verification engineer will develop a self-checking test suite
to verify design elements/functions specified by a design's
specification document. When the test suite contains all of the tests
required by the design specification, the test writer may be asking
him/herself, "How much logic in the design is actually being
exercised?", "Does my test suite cover all of the logic under test?",
and "Am I done writing tests for the logic?". When the design
verification gets to this point, it is often useful to get some
metrics for determining logic coverage. This is where a code coverage
utility, such as Covered, is very useful.
Please note that this package is for a stable release version.
There is a seperate package (covered-current) which is made of
development snapshots.
Diffstat (limited to 'print/teTeX2-bin/PLIST')
0 files changed, 0 insertions, 0 deletions