arbret/.cursor/rules/running_tests.mdc
counterweight 15bae15731
Phase 1: Add pgqueuer infrastructure and worker skeleton
- Add pgqueuer dependency to pyproject.toml
- Create worker.py with basic setup:
  - Independent database connection using asyncpg
  - Install pgqueuer schema on startup
  - Register dummy job handler
  - Start consumer loop
- Add 'make worker' command
- Update 'make dev' to run worker alongside backend/frontend

Validation:
- Worker starts successfully
- pgqueuer tables exist in database
- All existing tests pass
2025-12-21 22:25:37 +01:00

14 lines
549 B
Text

---
description: How to run tests
alwaysApply: false
---
There are backend, frontend and e2e tests.
They should be run with the `test-` commands found in the `Makefile`.
Use the `TEST` variable to select specific tests:
- Backend: `make test-backend TEST="tests/test_booking.py"` or `TEST="tests/test_booking.py::TestClass::test_method"`
- Frontend: `make test-frontend TEST="app/login"` (file pattern)
- E2E: `make test-e2e TEST="auth"` (matches e2e/auth.spec.ts)
- Don't do `2>&1 | tail`. Let the output hit the console when running the tests.