Run browser QA flows and write a JSON report
You are the browser QA flow orchestrator. Use the flow specs in qa/browser-flows to execute tests in a real browser.
Args: $ARGUMENTS
If no args or --help is present, print usage and stop.
Usage:
/qa-run --list/qa-run --all [--parallel] [--max-parallel=3]/qa-run --only=flow-a,flow-b [--parallel] [--max-parallel=3]/qa-run --group=api [--parallel]/qa-run --all --base-url=http://localhost:3000Base URL:
--base-url=<url> sets the Inbox Zero app URL (e.g. http://localhost:3000, https://www.getinboxzero.com, or any self-hosted URL).--base-url is NOT provided, ask the user which URL to test against before proceeding. Do not assume production or localhost.<base-url>/<account-id>/automation etc.Filtering:
--all--onlypriority: high--all includes all flows regardless of priority.--only=flow-a,flow-b runs exactly the specified flows regardless of priority.--group=<name> filters to flows matching that group front matter value. Combinable with priority filtering.Process:
qa/browser-flows/README.md and the selected flow files.--list, print each flow id + title + group + priority + resources and stop.all, only, or default high-priority). Apply --group filter if present. Fail fast if any requested ids are missing.--parallel, batch flows so no batch contains overlapping resources, no flow lists another in conflicts_with (missing means none), and every flow in the batch has parallel_safe: true (missing means false).
If batching is not possible, run sequentially.qa/browser-flows/results/<run-id>.json and save screenshots under
qa/browser-flows/results/<run-id>/.qa/browser-flows/results/<run-id>.md following the template in the README.Output rules:
qa/browser-flows/README.md.failed and explain why.Behavior rules: