Testing Protocol

After implementing any feature, run this protocol before marking complete.

Why This Protocol

This protocol exists because of real patterns observed across projects:

Unit tests pass ≠ user experience works. E2E testing captures real flow problems that no unit test detects: loading states, double-submit, empty states, network errors, responsiveness. E2E is the only guarantee that the user experience works.
Accessibility is invisible until it breaks. A screen reader user can't navigate your beautiful UI. WCAG audits catch contrast, keyboard navigation, and ARIA issues before users do.
AI-generated code has 1.7x more bugs (CodeRabbit 2025). Parallel review by fresh-context reviewers catches over-generation, unnecessary complexity, and slop that original author blindspots miss.
Interactive features need real interaction. Static analysis can't test loading states, error recovery, or edge cases that only appear in browser.

This protocol is the gate between "I finished coding" and "this is ready to ship."