What problem does it solve?
QA ensures a reviewer can confidently verify that a shipped or in-review change actually works as expected against the acceptance criteria, without turning QA into slow back-engineering.
Core Features & Use Cases
- Reviewer-triggered QA pass: Run verification when someone is picking up a change, not as part of the main build pipeline.
- Test-first verification: Executes the project’s existing tests relevant to the change, records pass/fail, and escalates failures as QA findings.
- Playwright e2e generation (when missing): Generates Playwright end-to-end checks for acceptance criteria when no existing e2e coverage exists, then runs them and captures traces/screenshots.
- Subtask-by-subtask QA: If the target Jira ticket has subtasks, QA them one at a time rather than treating the whole epic as a single pass.
- Human-friendly sign-off workflow: Produces a qa.md pass/fail artifact, offers interactive qa.html for manual checks, and lists any reviewer-required steps that can’t be safely automated.
Quick Start
Run /casaflow:qa CAS-NNNN to verify the change against its acceptance criteria, generate e2e checks if needed, and produce qa.md with pass/fail results.