Ngenaire Docs
Log inSign up free

Test Executions

Test Executions is the running record of verification activity — one row per run of a test case against a specific build. It keeps the full history so you can speak to trends, regressions, and "what was the last result on rc-3 vs. rc-4."

Open it from the sidebar under Verify → Test Executions, at /projects/:projectId/verification/executions.

What you see

  • Summary tiles — Total, Pass %, Fail %, Blocked, and Skipped, all reflecting the current filters.
  • Pass rate by build — a stacked bar chart of passed / failed / blocked / skipped counts per build label, with a pass-rate overlay.
  • Filter bar — search (case ID, title, executor, notes), plus filters for test case, build label, result, executed-by, and date range. A Reset and an Export CSV action sit in the actions row.
  • Run log table — Test Case, Result badge, Build, Executed At, Executor, Evidence count, and a Notes preview.

Recording a run

  1. Click Record Run to open the modal.
  2. Choose the Result — passed, failed, blocked, or skipped.
  3. Enter a Build label — a free-form, queryable string such as a release tag (v1.2.0-rc3), a nightly slug (nightly-2026-05-22), or a sprint id (sprint-12). The trend chart groups by exact match, so keep the scheme consistent.
  4. Optionally set the Executor (defaults to you; pick another member if you ran the test on their behalf), add a duration, paste evidence links (logs, screenshots, reports), and write notes (observed-vs-expected, anomalies, equipment serials).
  5. Click save.

When you save, the requirement's verdict in the RVTM updates immediately — a failure trumps a pass, and a requirement only reads "Verified" once every linked case has at least one passing run.

Summaries

The execution history rolls up two ways:

  • Per test case — pass / fail / blocked / skipped counts and the latest result for each case.
  • Project-wide — the same counts aggregated across every test case, with an overall pass rate.

These summaries feed the Coverage heatmap and the Verification Report.

Quick log

For one-off runs against a single test case, open Test Case Detail and use the quick-log buttons there. They reuse the last build label seen for the project so you don't have to retype it.

Filtering tips

  • Compare two builds — filter by build and export CSV, or read the build chart directly.
  • Find what's red on the latest build — set the build filter to the latest tag and the result to failed.
  • Per-executor accountability — filter by executor to see what one engineer ran, useful where independence matters.

Related