Testing - Lucim

Write a failing test before implementation and verify the relevant unit, integration, type, lint, and build checks before claiming a change is complete.

Backend

docker exec lucim-backend-dev pytest tests/ -v
docker exec lucim-backend-dev pytest tests/unit/ -v
docker exec lucim-backend-dev python -m mypy app/
docker exec lucim-backend-dev ruff check app/

Use the repository wrapper when database isolation matters:

./scripts/test-backend.sh

The wrapper provisions a uniquely named disposable test database and drops it on every exit path. The root pytest fixture rejects the shared development database and databases not explicitly marked as test-only.

Frontend

cd frontend
npm run typecheck
npm run lint
npm run test:run
npm run build

Migrations

docker exec lucim-backend-dev alembic upgrade head
docker exec lucim-backend-dev alembic check

Generate an intentional migration only after its model change and failing test are in place:

docker exec lucim-backend-dev alembic revision --autogenerate -m "describe change"

High-risk capabilities

Repository scanning, dependency evidence, Joern, external providers, and sandbox execution have dedicated hermetic and external conformance suites. Unit tests must never enable a production gate or write conformance settings as a side effect.

​Backend

​Frontend

​Migrations

​High-risk capabilities

Backend

Frontend

Migrations

High-risk capabilities