diff options
author | kamil <kamil> | 2016-10-08 14:31:33 +0000 |
---|---|---|
committer | kamil <kamil> | 2016-10-08 14:31:33 +0000 |
commit | 489d3180c95f454a6592196fcebb95b26359bc93 (patch) | |
tree | bc9ce238b726feeb780f22b1bde982a98f38f046 /cad/covered-current/DESCR | |
parent | 86c1e7250f0ac3f0a332c39c80cb985aa2123c52 (diff) | |
download | pkgsrc-489d3180c95f454a6592196fcebb95b26359bc93.tar.gz |
Drop covered-current
It used to track cad/covered but the last upgrade happened to be 20060904.
Diffstat (limited to 'cad/covered-current/DESCR')
-rw-r--r-- | cad/covered-current/DESCR | 17 |
1 files changed, 0 insertions, 17 deletions
diff --git a/cad/covered-current/DESCR b/cad/covered-current/DESCR deleted file mode 100644 index 430a2339c08..00000000000 --- a/cad/covered-current/DESCR +++ /dev/null @@ -1,17 +0,0 @@ -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 a development snapshot and while it -contains the latest and greatest features, it may be buggy as well. -There is a separate package which is made of the stable releases. |