Test Strategy

4. Define coverage targets

• Statements >= 80%, Branches >= 75%, Functions >= 80%, Lines >= 80%.
• Critical modules (auth, payments): >= 90%.

5. Create test directory structure

tests/
  unit/          ← mirrors src/ structure
  integration/   ← API + DB tests
  e2e/           ← browser flow tests
  fixtures/      ← shared test data
  helpers/       ← test utilities

6. Document testing conventions

• File naming: <module>.test.ts or <module>.spec.ts.
• Use describe blocks per module, it blocks per behavior.
• Prefix test descriptions with "should".
• Keep tests independent — no shared mutable state.

7. Add test scripts to package.json

{
  "scripts": {
    "test": "vitest run",
    "test:watch": "vitest",
    "test:unit": "vitest run tests/unit",
    "test:integration": "vitest run tests/integration",
    "test:e2e": "playwright test",
    "test:coverage": "vitest run --coverage"
  }
}

8. Configure CI integration

• Run unit + integration tests on every PR.
• Run E2E tests on merge to main or nightly.
• Fail PR if coverage drops below thresholds.