run-reportlisted

Produce an execution report from a Playwright run in the formats the QA profession consumes - JUnit XML, Cucumber JSON, and a self-contained HTML summary - with requirement traceability. Use after running an automated suite, when a CI dashboard or an ALM needs the results, or when someone asks what the last run actually produced.
QAIA-Project/QAIA · ★ 0 · Testing & QA · score 64

Install: claude install-skill QAIA-Project/QAIA

# run-report — execution reporting The three reporting formats real QA toolchains actually ingest, plus requirement traceability. ## Outputs - **JUnit XML** — for CI dashboards and most ALMs. Native Playwright reporter. - **Cucumber JSON** — for import into Xray (git-master mode: the repo is the source of truth) and BDD reporters. **Playwright has no Cucumber JSON reporter**; this is a conversion QAIA performs from the native `json` reporter. Procedure and field mapping: `references/cucumber-json.md`. - **Self-contained HTML** — human-readable summary: pass/fail by scenario ID, per-type breakdown (e2e/api/a11y/perf/security), and the AC → scenario → test → result traceability table. Structure: `references/html-summary.md`. - **Standardized run manifest** — merge the results into `.qaia/reports/<US-ID>/manifest.json` per the shared output contract ([`docs/OUTPUT-CONTRACT.md`](https://github.com/QAIA-Project/QAIA/blob/main/docs/OUTPUT-CONTRACT.md)), so scoring and dashboards read execution the same way they read the test book. ## Steps 1. Configure the reporters in `playwright.config.js`, and map test titles' `@QAIA-*` tags to requirement IDs: ```js reporter: [ ['list'], ['junit', { outputFile: 'junit.xml' }], ['json', { outputFile: 'results.json' }], // source for the Cucumber conversion ], ``` 2. After a run, produce the three outputs. **Never fabricate a result the run did not produce** — a report is downstream of an ex