← ClaudeAtlas

qa-export-evidencelisted

Build QA test evidence for a web app's export buttons (CSV / Excel / PDF / Print) and turn it into an .xlsx test report: walk each page on a signed-in CDP Chrome, screenshot every step (page → filter → result → export button → queued alert → queue modal → the downloaded file opened), verify the file with a real parser, then write a workbook with a Summary sheet and one sheet per case (B2 title · B4 Test Result · B5 Test Environment · B6 Test Date · B7 Actual Result · captioned screenshots in a 2-column grid). Use WHENEVER the work is "test evidence for export", "test the Export Excel/PDF/CSV buttons", "QA test report xlsx", "ทดสอบปุ่ม Export", "หลักฐานการทดสอบ export", "make_qa_report", or a request to rebuild a QA report workbook from an evidence folder.
th3r-dev/th3-skills · ★ 2 · Data & Documents · score 66
Install: claude install-skill th3r-dev/th3-skills
# QA evidence for export buttons **In** a list of pages × formats on one environment · **Out** `<run>/` with `cases.json`, `evidence/` (one folder per case: `steps.csv`, `run.json`, the downloaded file, `screenshots/`), and the report `.xlsx`. ```bash RUN=qa-reports/<run> # change this line only S=skills/qa/export-evidence/scripts # a Chrome with remote debugging, signed in by a person: # chrome --remote-debugging-port=9222 --user-data-dir=~/.cache/qa-chrome [--headless=new] uv run $S/collect_export.py $RUN/cases.json $RUN/evidence # all cases uv run $S/collect_export.py $RUN/cases.json $RUN/evidence <slug> # re-run one; the others stay uv run $S/make_qa_report.py $RUN/evidence --out $RUN/<name>.xlsx \ --title "<Summary title>" --env UAT --date "NOV 9, 2026" \ [--only-sheets "reports export excel"] [--labels references/labels-th.json] ``` Both scripts only read and write **inside the folder they run from** (`cases.json`, the evidence dir, `--out`, `--labels`); run them from the repo root. 1. **Inventory from source, not from clicking around.** The app's menu / route config plus the page templates show which pages carry an export bar. Write the list down with the kind of export each one uses (see below) — the page set changes between releases, so re-check before each run. 2. **Write `cases.json`.** One case per page × format. `sheet` names the group a case belongs to (`--only-sheets` splits one run into seve