Julian Tabel
bf3a3d3329
Lint, formatting, and type checks are already enforced by prek pre-commit hooks, so CI now focuses on running the actual test suites instead. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1.2 KiB
1.2 KiB
title, status, type, priority, created_at, updated_at
| title | status | type | priority | created_at | updated_at |
|---|---|---|---|---|---|
| Implement Unit & Integration Tests | completed | epic | high | 2026-02-10T09:32:47Z | 2026-02-21T13:00:44Z |
Add comprehensive unit and integration test coverage to both the backend (FastAPI/Python) and frontend (React/TypeScript). The project currently has zero tests — pytest is configured in pyproject.toml with pytest-asyncio and httpx, but no actual test files exist. The frontend has no test tooling at all.
Scope:
- Unit tests for isolated logic (schemas, services, utilities)
- Integration tests for API endpoints (using httpx AsyncClient against a test database)
- Frontend unit/component tests (using Vitest + React Testing Library)
Explicitly out of scope:
- End-to-end / browser tests (e.g. Selenium, Playwright) — requires specialised infrastructure
Success Criteria
- Backend test infrastructure is set up (conftest, fixtures, test DB)
- Backend schemas and services have unit test coverage
- Backend API endpoints have integration test coverage
- Frontend test infrastructure is set up (Vitest, RTL)
- Frontend utilities and hooks have unit test coverage
- Frontend components have basic render/interaction tests