Testing Engineering

Purpose

Tests are the only mechanism that proves the code does what the plan says it should. For vibe-coders, this is the most skipped step - and the one that causes the most production incidents. This skill does not treat tests as optional polish; it treats them as a deliverable equal in importance to the feature itself.

Progressive Disclosure

• Load references/pytest-patterns.md for advanced fixtures, parametrize, and async test patterns.
• Load references/playwright-e2e.md for page object model and multi-browser E2E patterns.

SOP: Testing Strategy

Step 1 - Define the Testing Pyramid for This Feature

Before writing any test, identify what layer of the pyramid applies:

         [E2E Tests]           <- Few, slow, highest confidence (Playwright)
       [Integration Tests]     <- Some, moderate speed (pytest with real DB)
     [Unit Tests]              <- Many, fast, isolated (pytest with mocks)