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
+6-1Lines changed: 6 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -942,7 +942,12 @@ Every `qa suite` run writes top-level `qa-evidence.json`,
942
942
`qa-suite-summary.json`, and `qa-suite-report.md` artifacts for the selected
943
943
scenario set. Scenarios that declare `execution.kind: vitest` or
944
944
`execution.kind: playwright` run the matching test path and also write
945
-
per-scenario logs. When `qa suite` is reached through
945
+
per-scenario logs. Scenarios that declare `execution.kind: script` run the
946
+
evidence producer at `execution.path` through `node --import tsx` (with
947
+
`${outputDir}` and `${scenarioId}` expanded in `execution.args`); the producer
948
+
writes its own `qa-evidence.json`, whose entries are imported into the suite
949
+
output and whose artifact paths are resolved relative to that producer
950
+
`qa-evidence.json`. When `qa suite` is reached through
946
951
`qa run --qa-profile`, the same `qa-evidence.json` also includes the profile
947
952
scorecard summary for the selected taxonomy categories.
948
953
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.
0 commit comments