Skip to main content

Development & testing

A Makefile at the repo root wraps the day-to-day commands so you don’t have to remember the uv incantations.

Targets at a glance

Using an existing virtualenv

By default uv manages its own .venv (created by make install-dev). If you keep your dev environment elsewhere — e.g. a micromamba env — point uv at it once and make picks it up:
Drop the export into your shell rc (or a direnv .envrc) and forget about it. Without --extra dev, pytest-asyncio is missing and you’ll see “async functions are not natively supported” across every async test — same trap on a fresh env.

Platform-side test suite

The platform-side test suite is separate and lives at platform/api/tests/: