Ngenaire Docs
Log inSign up free

Verification Report

The Verification Report turns your test executions and coverage into a single deliverable that answers "what is verified, and what is not?" It assembles an executive summary, a per-requirement results table, and closure evidence suitable for stakeholder and design reviews (PDR, CDR, TRR).

Open it from the sidebar under Verify → Verification Report, at /projects/:projectId/verification/report. The older /projects/:projectId/verification/overview route redirects here.

What you see

  • A summary of verification status — percent passed, percent failed, and percent not run across the requirement set.
  • A traceability table of each in-scope requirement with its verification method, reference, and current status (rolled up from the latest test execution per linked case).
  • The report's metadata — report ID, version, and status.

Walkthrough

  1. Open Verify → Verification Report.
  2. Click the create action to start a new report, or select an existing one.
  3. Use Generate to have the AI draft the report's narrative from the current executions and coverage. You can scope the generation to a specific build label so the report speaks to one configuration.
  4. Review the summary and traceability table. If a requirement still needs a run, record it from Test Executions — the report reflects the new result on its next load.
  5. Set the report's status (for example, mark it Approved). A report can only be approved once every in-scope requirement is verified or explicitly justified.

Export

Use the Export controls to download the report:

  • PDF — the formatted document with the executive summary, traceability table, and results, suitable for reviews.
  • Markdown — the same content as portable text.

Archived requirements

Saved reports keep the requirement set that was in scope when they were generated. When a report is viewed or exported, any requirement that has since been archived is filtered out of the displayed list and result rows. The saved data is unchanged — restore the requirement and it reappears on the next read.

Tips

  • Treat the report as the source of truth. Any verification claim made outside Ngenaire should reference a run captured here.
  • Close failed runs explicitly. A failure should be fixed and re-run, or accepted with a documented justification.
  • Re-export after each round of testing. An export is a snapshot of where the project stood at that moment.

Related