Ngenaire Docs
Log inSign up free

Test Case Detail

Test Case Detail is the page for a single test case. Reach it by clicking a test-case code anywhere in the app (the Test Procedures page, the Coverage heatmap, the network view, or search). URL: /projects/:projectId/verification/test-cases/:testCaseId.

Test cases — together with Test Executions — are how Ngenaire tracks verification today. They replaced the retired "verification objects" concept.

Layout

  • Header — the test-case code and title, with the case description as the subtitle.
  • Quick-log strip — the last result badge plus Passed / Failed / Blocked / Skipped buttons and a Record Run… affordance for the full modal.
  • Tabs:
    1. Overview — status, verification method, preconditions, expected results, pass/fail criteria, and notes.
    2. Steps — the numbered steps, each with its action and expected observation.
    3. Procedure — the parent test procedure (when set), with its purpose, preconditions, and equipment surfaced inline.
    4. Execution History — a trend chart of recent runs colored by result, followed by the full table.
    5. Linked Requirements — chips for every requirement this case verifies; click one to jump to it.

Quick-log buttons

The four single-click buttons record a minimal execution against the last build label the project saw. If the project has no prior execution, the full Record Run… modal opens so you can supply a build label explicitly. A toast confirms the saved result and build, and the requirement's RVTM status updates in the same tick.

Record Run modal

The same modal used on the Test Executions page, pre-filled with this test case and the last-used build label. It captures the result, build label, executor, duration, evidence links, and notes.

Generating a test case with AI

You don't create a test case from this page — you reach this page after one exists. To draft a starter test case for a requirement, use the AI test-case generator from the Requirements page; review and refine it on the Test Procedures page.

Editing the case

The Edit button in the header opens the Test Procedures page with this case selected, where you can change its steps, pass/fail criteria, and verification method.

Trace links

Linked requirements are bidirectional — adding a test-case code to a requirement's RVTM row populates this case's Linked Requirements tab, and clicking a chip jumps to the requirement.

Related