Reporting of assertion coverage

In reply to ben@SystemVerilog.us:

Hi Ben,

Thanks for the response. Good info on API’s. I was hoping not to have to customize my reporting, since it seems like a common task that Questa should roll up all coverage and assertion grading into a single number per module, so I can scan a report and see the complete status of each module in one column, including coverage and test failures. I think I’ll take my first question over to a Modelsim/Questa support site.

My second question again seems like a common problem which I assume someone should have written a page of documentation regarding pairing assertions and cover statements, where the cover statements ensure the inputs to the logic are stimulated for all cases, and the assertion ensures that the outputs are correct for the given input conditions. Am I using assertions in a non-standard way? Or perhaps this is a basic occurrence which requires no detailed discussion. I was hoping to glean some hints on a “formula” for ensuring that I don’t miss something in my cover statement, based on a given assertion statement.

Thanks for your time!