You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/concepts/qa-e2e-automation.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -915,6 +915,7 @@ The report should answer:
915
915
For the inventory of available scenarios - useful when sizing follow-up work or wiring a new transport - run `pnpm openclaw qa coverage` (add `--json` for machine-readable output).
916
916
When choosing focused proof for a touched behavior or file path, run `pnpm openclaw qa coverage --match <query>`.
917
917
The match report searches scenario metadata, docs refs, code refs, coverage IDs, plugins, and provider requirements, then prints matching `qa suite --scenario ...` targets.
918
+
When a scenario declares `execution.kind: vitest` or `execution.kind: playwright`, `qa suite --scenario <scenario-id>` runs the matching test path and writes `qa-vitest-report.md` or `qa-playwright-report.md`, per-scenario logs, and `qa-evidence.json`.
918
919
Treat it as a discovery aid, not a gate replacement; the selected scenario still needs the right provider mode, live transport, Multipass, Testbox, or release lane for the behavior under test.
919
920
920
921
For character and style checks, run the same scenario across multiple live model
0 commit comments