User guide

20-39
Using OpenVera Assertions
Reporting
By default, the assertion report generated by the OVA engine is
written into ./simv.vdb/report/ova.report. In the case of multiple
post-processing runs, there is a chance the file will be overwritten.
For each run, it is suggested that the -ova_report name.report
and -ova_name name options be used to ensure that any report
files generated will be stored under unique names.
Coverage
To enable functional coverage, use the -ova_cov option during the
Step 2 (-ova_RPP) compile (also enter -ova_cov_events to see
coverage of events). During the post-processing run, the -ova_cov
option must again be given (as a runtime option) to actually turn on
coverage capture.
By default, the coverage from all post-processing runs with a given
compiled OVA image is captured in a single database. If you need to
generate reports for each post-process run separately, use the
-ova_cov_name name option to assign a unique name to each
post-processing run. The various databases are stored under the
simv.vdb directory in either case. Coverage reporting can include a
single post-processing run or a merged set of runs, as described in
the OVA chapter of the VCS/VCSi User Guide.
Coverage reports are generated with the fcovReport utility. The
fcovReport command line should include the -ova_cov_db vdbdir
option to point to the directory where the global coverage database
resides, and the -ova_cov_report name to point to the path and
name of the report file.