Repository navigation
Associative Coverage Merge in Riviera-PRO #83
Description
Activity
Please list what you would like the command line changed to. Is it appropriate to always set this option? It should be an easy add. It may require a SetExtendedMergeOptions to make the setting optional and/or configurable.
The command line would be changed to:
acdb merge -associative -o ${CoverageFileBaseName}.acdb -i {*}[join $CovFiles " -i "]From what I can tell from the Riviera documentation, the
-associativeoption just includes additional information in the merged database and it should be fine to always set. Using the OSVVM 2025.06a release, I ranbuild RunDemoTestsWithCoverage.proboth with and without the option set. With the option set, the merged database file was about 11% larger. The cumulative coverage numbers in the html report were identical, but the report shows handy information about which test(s) cover each statement or branch:
This can now be selected by setting the variable ExtendedMergeOptions to "-associative" - which is now the default for RivieraPro, ActiveHDL, and VSimSA. These updates are on the Dev branch and will move to the main branch during the next release
In addition to the standard code coverage report, I like to use the coverage ranking feature of Riviera-PRO to determine how each test case contributes to the total coverage. Unfortunately, I can't just call
acdb rankon the build's merged coverage database sincevendor_MergeCodeCoveragedoesn't use the-associativeoption foracdb merge. It would be nice to have this option enabled:OSVVM-Scripts/VendorScripts_RivieraPro.tcl
Line 287 in 20351e9