pokemon/nuzlocke-tracker
1
1
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Set up backend test infrastructure

Browse Source 
Add pytest fixtures (engine, db_session, client) with session-scoped
event loop to avoid asyncpg loop mismatch errors. Smoke tests verify
all three main API endpoints return empty results on a clean DB.
Test DB provided by docker-compose.test.yml on port 5433.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Julian Tabel
2026-02-21 12:35:22 +01:00
parent 16f9e68821
commit b0ac3714a9
6 changed files with 782 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

31
.beans/nuzlocke-tracker-rrcf--set-up-backend-test-infrastructure.md
View File

@@ -1,11 +1,11 @@
---
# nuzlocke-tracker-rrcf
title: Set up backend test infrastructure
status: draft
status: completed
type: task
priority: normal
created_at: 2026-02-10T09:32:57Z
updated_at: 2026-02-10T09:33:59Z
updated_at: 2026-02-21T11:33:32Z
parent: nuzlocke-tracker-yzpb
blocking:
- nuzlocke-tracker-hjkk
@@ -18,19 +18,18 @@ blocking:
Set up the foundational test infrastructure for the FastAPI backend so that all subsequent test tasks can build on it.
## Approach
- Session-scoped async engine: creates all tables once via `Base.metadata.create_all()`, drops them after all tests finish
- Function-scoped `db_session` fixture: provides a fresh `AsyncSession`, overrides the `get_session` FastAPI dependency, and truncates all tables after each test for isolation
- Function-scoped `client` fixture: `httpx.AsyncClient` with `ASGITransport` — hits the real app stack including middleware and routing
- `asyncio_default_fixture_loop_scope = "session"` and `asyncio_default_test_loop_scope = "session"` added to pyproject.toml so all fixtures and tests share the same session event loop (required to avoid asyncpg "Future attached to different loop" errors)
- Test database URL read from `TEST_DATABASE_URL` env var (default: `postgresql+asyncpg://postgres:postgres@localhost:5433/nuzlocke_test`)
- The test DB is provided by `docker-compose.test.yml` (postgres on port 5433, `nuzlocke_test` DB created automatically)
## Checklist
- [ ] Create `backend/tests/conftest.py` with shared fixtures
- [ ] Set up a test database strategy (use a separate test PostgreSQL database or SQLite for speed — evaluate trade-offs)
- [ ] Create an async test client fixture using `httpx.AsyncClient` with the FastAPI `app`
- [ ] Create a database session fixture that creates/drops tables per test session or uses transactions for isolation
- [ ] Add factory fixtures or helpers for creating common test entities (games, pokemon, runs, etc.)
- [ ] Verify the setup works by writing a simple smoke test (e.g. health endpoint returns 200)
- [ ] Document how to run tests (e.g. `pytest` from backend dir, any env vars needed)
## Notes
- pytest, pytest-asyncio, and httpx are already in pyproject.toml dev dependencies
- AsyncIO mode is set to "auto" in pyproject.toml
- The app uses SQLAlchemy async with asyncpg — test fixtures need to handle async session management
- Consider using `SAVEPOINT`-based transaction rollback for test isolation (faster than recreating tables)
- [x] Add `asyncio_default_fixture_loop_scope = "session"` and `asyncio_default_test_loop_scope = "session"` to `pyproject.toml`
- [x] Create `backend/tests/conftest.py` with `engine`, `db_session`, and `client` fixtures
- [x] Write a smoke test in `backend/tests/test_smoke.py` to verify the setup
- [x] Verify all tests pass (`pytest` from backend dir)