project-testinglisted

<!-- Generated by ai-dev-kit:recommend-skills on {date} --> <!-- This skill can be safely deleted if no longer needed --> # {project} Testing Patterns Custom testing patterns, fixtures, and strategies for this project. ## Variables | Variable | Default | Description | |----------|---------|-------------| | COVERAGE_TARGET | 80 | Minimum coverage percentage | | E2E_TIMEOUT | 30000 | E2E test timeout in ms | | PARALLEL_TESTS | true | Run tests in parallel when possible | ## Instructions 1. Identify test type needed (unit/integration/e2e) 2. Use appropriate fixtures and patterns 3. Follow project naming conventions 4. Ensure proper cleanup ## Red Flags - STOP and Reconsider If you're about to: - Write a test without proper isolation - Skip cleanup in fixtures - Hardcode test data instead of using fixtures - Write flaky tests (timing-dependent, order-dependent) **STOP** -> Use proper fixtures -> Ensure isolation -> Then write test ## Test Categories ### Unit Tests Location: `tests/unit/` Patterns: - Test single functions/methods in isolation - Mock external dependencies - Fast execution (< 100ms each) ### Integration Tests Location: `tests/integration/` Patterns: - Test component interactions - Use test database/fixtures - May have external dependencies ### E2E Tests Location: `tests/e2e/` or `playwright/` Patterns: - Test full user workflows - Use browser automation - Longer execution time acceptable ## Fixtures ### Database Fixtures Location: `tests/fixtur