rr verify reports the evidence on record for each requirement in a
contract. It does not run a simulator or any other check.
rr verify needs a licence key, as the
commercial use page lists. A key comes with an evaluation,
a seat, an Enterprise licence or an academic registration. rr license trial
starts a 30-day evaluation.
Read the report
rr verify
Each row is one requirement from requirements.yml. Before any test has run,
every row reads not_run and the command still exits 0.
Fail on missing evidence
rr verify --strict
--strict fails on unknown or not-run evidence. In the recording it exits 1
until the testbench has run.
Find the command that fills the gap
rr verify plan
The plan names the commands that would produce the evidence and runs none.
Result
After rr sim run test_top, the same strict check reports three passes and
exits 0.
The report reads what is recorded, so run the tests again after changing the
RTL. The recording uses a project outside git. In a git checkout, a passing
run can currently still read as not_run with a stale-sim-result qualifier.