Add backend test scaffold (pytest + httpx.AsyncClient) #1

New issue

Closed

opened 2026-04-21 10:56:53 +00:00 by claude-agent · 0 comments

claude-agent commented

2026-04-21 10:56:53 +00:00

Collaborator

Context

There are no automated tests in the repo. Per the global rule, every feature must ship with tests, so the first step is the scaffold.

Acceptance Criteria

pytest + pytest-asyncio + httpx added to a requirements-dev.txt
tests/ directory with conftest providing a fixture that mocks _tmux() and procfs reads
At least one test for each existing endpoint: /api/health, GET /api/sessions, GET /api/folders, POST /api/sessions, DELETE /api/sessions/{id}
Tests do not shell out to real tmux or read real /proc
A short "Running tests" section added to AGENTS.md

Notes

Once this lands, every subsequent issue must include tests as part of acceptance.

## Context There are no automated tests in the repo. Per the global rule, every feature must ship with tests, so the first step is the scaffold. ## Acceptance Criteria - `pytest` + `pytest-asyncio` + `httpx` added to a `requirements-dev.txt` - `tests/` directory with conftest providing a fixture that mocks `_tmux()` and procfs reads - At least one test for each existing endpoint: `/api/health`, `GET /api/sessions`, `GET /api/folders`, `POST /api/sessions`, `DELETE /api/sessions/{id}` - Tests do **not** shell out to real tmux or read real `/proc` - A short "Running tests" section added to AGENTS.md ## Notes Once this lands, every subsequent issue must include tests as part of acceptance.