Test cases
Browse every test case, open its detail sheet for steps, procedure, linked requirements and run history, and log a result in one click.
Test cases are the unit of verification in Ngenaire. Each one verifies one or more requirements, and its runs — recorded as test executions — drive the requirement's status in the RVTM. The Test cases page lists them all; selecting one opens its detail sheet.
Where: sidebar Verify → Test cases ·
/p/<project>/verification/cases
The list
Every test case in the project, with its code, title and status. Search and filter to narrow it, then select a row (or press Enter on it) to open the detail sheet.
Each case is deep-linkable: /p/<project>/verification/cases?item=TC-000003 opens the list with that case's sheet already open. Any TC- code you see elsewhere — in a procedure, the RVTM, the coverage heatmap, a notification or the command palette — leads here.
Create a test case
- Click New test case on the page, or press ⌘K and run New test case.
- Or add one from its procedure with Add Test Case; see Test procedures.
- Or draft starter cases from a requirement with Generate test cases with AI on the All requirements tab.
The detail sheet
The header shows the code, title and description, with a quick-log strip beneath it. The body is organised in tabs:
- Overview — status, priority, owner, verification method (Test, Analysis, Demonstration or Inspection), objective, preconditions, expected results, pass/fail criteria and notes.
- Steps — the numbered steps, each with its action and expected observation.
- Procedure — the parent test procedure, when set, with its purpose and scope shown inline.
- Execution History — a trend chart of recent runs coloured by result, then the full run table: result, build, executed at, executor, evidence and notes.
- Linked Requirements — a chip for every requirement this case verifies; select one to open it.
Edit any field directly in the sheet. Comments and history sit alongside, as on every other object.
Quick log
The quick-log strip shows the Last result and four one-click buttons: Passed, Failed, Blocked and Skipped. Each records a minimal run against the last build label the project used, so you don't retype it. If the project has no runs yet, the full Record Run dialog opens instead so you can enter a build label.
A toast confirms the saved result and build, and the requirement's status in the RVTM updates at the same moment.
Record a full run
Record Run opens the same dialog as the Test executions page, pre-filled with this case and the last-used build label. It captures the result, build label, executor, duration, evidence links and notes.
Trace links
Links between test cases and requirements are bidirectional. A requirement in this case's Linked Requirements shows the case in its RVTM row's Linked test cases, and the link appears on the Trace graph. Selecting either end takes you to the other.
Co-engineer prompts
Review TC-000003 and tighten its pass/fail criteria so they are measurable.
Which test cases failed on the latest build, and which requirements do they block?