Covered - Assertion Coverage
Author: Trevor Williams

|  |  | 8
User Manual - «Covered»
|  |  | 2.4 Assertion Coverage
|  |  | Assertion coverage answers the question, "Did I hit all of the possible coverage points of the assertions that I included in the design?"
|  |  | Currently, Covered is capable of finding all OVL (Open Verification Language) assertion modules instantiated within the design (when the -A ovl option has been specified to the score command). Within most OVL assertion modules are one or more built-in coverage points. When the user has specified a particular assertion instance to check for a coverage point, Covered simulates this assertion module, keeping track of which coverage points within the assertion have been hit during simulation (and how many times each coverage point has been hit) and which have not. This allows the user to check for more complex coverage scenarios within the design.
|  |  | Currently, only OVL version 1.6 (and newer) are supported. Older versions of the OVL may not work and are not planned to be supported.
|  |  | 2.4.1 Recommendations
| Recommendations |  | For a design to pass full coverage, it is recommended that the assertion coverage for all modules in a design receive 100% coverage. If an assertion coverage point is not hit during simulation, the design has not been fully exercised. Assertion coverage is useful for determining more specific corner case holes in the test suite.
|  |  | [ 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.