Browser QA Runbook
Use Chrome DevTools MCP for browser-first checks on PixelFPS.
First smoke pack
- Homepage loads without console errors
- Auth flow works for login, logout, and bad-credential handling
- Stats and rankings pages render without failed XHR or blank states
- Lobby and matchmaking flows can enter, cancel, and recover cleanly
What to capture every run
- one full-page screenshot per major route
- console errors and warnings
- failed network requests
- obvious layout breaks on desktop width and mobile width
Pass criteria
- no uncaught console errors
- no 5xx requests on core routes
- no dead buttons on primary actions
- no blocking visual regressions on homepage, auth, stats, rankings, lobby
Suggested execution order
- Homepage
- Auth
- Stats
- Rankings
- Lobby
- Matchmaking
Notes
- keep this focused on user-visible breakage, not pixel-perfect polish
- attach screenshots and request failures to any bug report