Scenario guide场景指南
Browser QA
Validate user-facing flows with evidence.
The problem · 要解决的问题
User-visible releases need browser-level proof: screenshots, console checks, interaction coverage, and a repeatable loop when something breaks.
Recommended skills推荐 skill
4 picks · Best pick first, ranked by fit★ best fit · 首选
QA Loop
by Anya Raghavan
Best fit for repeatable browser QA with screenshots, issue reproduction, and fix verification.
- Browser automation
- Screenshot evidence
- Acceptance workflow
GStack QA
by Garry Tan
Strong browser-first alternative when the user wants a tighter fix-and-reverify loop.
- Explores user flows
- Captures console and visual evidence
- Can iterate on verified bugs
Canary Watch
by Joel Martinez
Better after deploy than during local QA, especially for route sampling and visual drift checks.
- Post-deploy monitoring
- Console error checks
- Visual drift awareness
Test Bench
by Anya Raghavan
A useful companion when browser QA exposes coverage gaps that should move into CI.
- Coverage suggestions
- Flaky test isolation
- CI-oriented advice