Test Master

If you're spending time debating what to test or chasing flaky CI runs, this walks you through the whole testing lifecycle: scoping, strategy, writing tests with proper assertions, and reporting coverage gaps. It covers unit, integration, E2E, performance (k6), and security testing with OWASP methods. The quick-start example shows the pattern it enforces: meaningful descriptions, specific assertions, mocked dependencies. Includes reference docs for TDD iron laws and testing anti-patterns adapted from Jesse Vincent's work. The constraints section is blunt about what breaks tests in production: order dependencies, truthiness checks instead of specific assertions, ignoring error paths. Honestly, the structured approach helps most when onboarding junior developers or standardizing test quality across a team.