Live Browser QA Pass
Run a hands-on quality-assurance pass on a running web app or page by actually exercising it in a browser, then emit a defect report with reproduction steps and severity. First derives a test plan and acceptance criteria from the app's intended behavior (happy paths, edge cases, error states, responsive/console health), then drives the UI step-by-step clicking and typing through each flow while watching the console and network for errors, then writes a bug report where every defect has numbered repro steps, expected vs actual, and severity. Use this for QA, manual testing, smoke testing, exploratory testing, click-testing a build, or verifying a feature works in the real browser before shipping — it finds broken flows, console errors, and visual breakage that unit tests miss.
How it runs
| # | Step | Who runs it | What happens |
|---|---|---|---|
| 1 | Plan the QA pass | Reviewer | enumerate flows + acceptance criteria to exercise |
| 2 | Exercise the app | Reviewer | drive each flow in a browser, capture defects |
| 3 | Write the QA report | Reviewer | emit a defect report with repro + severity |
| 4 | Evaluate | Reviewer | Grade the deliverable against every acceptance criterion. All pass → finish; any fail → loop back and fix the gap. |
| 5 | Finish | Developer | All acceptance criteria met. Stamp a short summary and report DONE. |
Say something like "qa this" or "run a qa pass" or "test this in the browser" or "smoke test the app" or "click through the app" or "manual test the feature" in chat to start it.