Acceptance run
What it's for
A single acceptance run's record: every scenario step from the template it was created against, each one's pass/fail state and evidence, and the go/no-go sign-offs recorded against it. This is where the actual testing happens, step by step, and where the record of who approved the rollout lives.
Reach it by opening a run from Customers → Acceptance runs, at
/acceptance-runs/[id].
Tabs
The record has no tabs. A status stepper across the header — Draft, In progress, Complete — shows where the run stands instead.
Panels and controls
- The header shows the run's short ID, its label, and a fact strip of org, scenario set and version, step count, and current pass rate. Prev/next arrows step through other runs.
- Start guided run (when the run has steps and isn't complete) opens the first step's screen directly.
- Publish to portal appears once the run has a customer attached and is still in draft — it makes the run visible to that customer in their portal.
- Mark complete closes the run out; Export run downloads it.
- The steps table lists each scenario's ID, label, and purpose, with an Open screen link straight to the part of the app it's testing. Each row's status badge shows pass, fail, or a suggested result with its source. Pass and Fail buttons record the human call — they're hidden once the run is complete.
- A suggested step shows an insight callout the office can accept or dismiss; notes and any uploaded evidence thumbnails sit under the step.
- Ingest automated check results lets you paste a Playwright manifest (a JSON array of check results) to seed suggested pass/fail marks in bulk. Ingested results land as Suggested only — they never stand in for the human Pass/Fail call, and this control honors the acceptance-run Off kill switch if automation is turned off for the shop.
- No steps is the empty state for a run with no scenario steps.
- The right rail's Summary card totals pass, fail, suggested, and pending counts. The Sign-off card lists recorded sign-offs (party, GO/NO-GO, date) or None yet, with a form to record a new one — party name, GO/NO-GO decision, and notes — hidden once the run is complete.
What it accepts
| Field | Format | Required | Rule |
|---|---|---|---|
| Step status | Pass or fail | Yes, per step | |
| Manifest JSON | A JSON array of check results | No | Ingested as suggested results only |
| Sign-off party | Free text (e.g. "thermal", "fieldboss", the customer's name) | Yes, to sign off | |
| Sign-off decision | GO or NO-GO | Yes, to sign off | |
| Sign-off notes | Free text | No |
How to configure it
- The Off/Suggest/Auto automation setting for acceptance runs decides whether ingested manifest results are allowed to populate suggested marks at all — with it off, ingestion has no effect.
- Whether a run can be published depends on the customer chosen when it was created, not a setting on this page.
Who can see it
This screen sits behind the Settings area.
Owners and office managers can open it. Dispatchers and technicians cannot. The gate is checked on the server, not just hidden in the sidebar, so a direct link does not get around it.
The full role matrix is on Roles & permissions.