Cursor rule

1---
2description: "Testing rules for pytest, integration tests, and E2E Docker framework."
3globs: "tests/**/*.py,tests/**"
4alwaysApply: false
5---
6 
7# Testing Rules
8 
9These rules apply when writing or modifying tests.
10 
11## Testing Stack
12 
13- **Unit/Integration**: pytest with pytest-asyncio
14- **E2E**: Docker-based framework (`docker-compose.test.yml`)
15- **Coverage**: pytest-cov
16 
17## Test Organization
18 
19```
20tests/
21  unit/           # Fast, isolated unit tests
22  integration/    # API and database integration tests
23  e2e/            # End-to-end tests (Docker required)
24```
25 
26## Running Tests
27 
28```bash
29# Unit tests
30pytest tests/unit/
31 
32# Integration tests
33pytest tests/integration/
34 
35# E2E tests
36pytest tests/e2e/
37# or: make test-e2e
38 
39# All tests
40pytest tests/ -v
41 
42# Full CI validation
43{{CI_VALIDATE_COMMAND}}
44```
45 
46## Test Patterns
47 
48### API Integration Tests
49 
50See `patterns_library/testing/api-integration-test.md` for the full pattern.
51 
52Key points:
53- Mock authentication for isolated testing
54- Verify RLS context is used (no direct ORM calls)
55- Test both success and error paths
56- Test authentication failures (401)
57- Test authorization failures (403)
58- Test input validation errors (422)
59 
60### E2E Tests
61 
62See `patterns_library/testing/e2e-user-flow.md` for the full pattern.
63 
64Key points:
65- Use `docker-compose.test.yml` for infrastructure
66- Test complete user journeys
67- Include login/auth setup in fixtures
68- Clean up test data after each run
69 
70## Writing Good Tests
71 
721. **Independent**: Tests must not depend on execution order
732. **Repeatable**: Same result every time, no flaky tests
743. **Clear naming**: `test_<what>_<condition>_<expected>`
754. **Arrange-Act-Assert**: Follow the AAA pattern
765. **Edge cases**: Cover boundary conditions, empty states, error paths
776. **RLS isolation**: Verify user A cannot access user B's data
78 
79## Coverage Requirements
80 
81- Business logic: Aim for high coverage
82- API endpoints: All routes should have integration tests
83- Security paths: Authentication and authorization MUST be tested
84- Error handling: All error responses MUST be tested
85 
86## Acceptance Criteria Verification
87 
88When testing a spec, map each acceptance criterion to at least one test:
89 
90```python
91# From spec: "User can create new resource"
92def test_user_can_create_resource():
93    ...
94 
95# From spec: "Validation shows errors for invalid input"
96def test_create_resource_invalid_input_returns_422():
97    ...
98 
99# From spec: "Unauthorized access returns 401"
100def test_create_resource_unauthenticated_returns_401():
101    ...
102```
103 
104## Key References
105 
106- `patterns_library/testing/` -- Test patterns (copy-paste ready)
107- `AGENTS.md` -- QAS role definition and validation commands
108- `CONTRIBUTING.md` -- CI pipeline test stages
109