Backend
¶ API
cd apps/api
ruff check .
mypy app
pytestDeveloper guide
¶ Testing Guide
Nothing except Alembic replay gates a production deploy. Run checks locally before promotion.
Only gate: Alembic replay
Everything else runs locally
Harnesses skip silently when unset
Gates a production deploy
Alembic replay
Your responsibility before promotion
API checks
Integration harnesses
Web checks
Connector checks
Deep-link tests
Checks per app
¶ Run the checks for every app you touched
Integration harnesses
¶ Unlock the DB and Redis tests
Integration tests that exercise DB/Redis require TEST_DATABASE_URL and TEST_REDIS_URL. Point them only at disposable instances.
A green run can hide skipped tests
When these variables are unset, the tests skip silently. Always check pytest's skip count before trusting a green run.
¶ TEST_DATABASE_URL
TEST_DATABASE_URL=postgresql+asyncpg://user:pass@localhost:5432/replybox_test pytest
Truncates between tests.
Use a disposable instance to avoid clobbering real data.
¶ TEST_REDIS_URL
TEST_REDIS_URL=redis://localhost:6379/15 pytest
Verifies behavior against real Redis/Lua.
Use logical DB 15 locally for integration runs.
DB tests that enqueue BullMQ jobs also need Redis. tests/conftest.py copies TEST_REDIS_URL to REDIS_URL, SOCKETIO_REDIS_URL, and RATE_LIMIT_REDIS_URL before importing app code, so always set TEST_REDIS_URL when running DB integration tests, in CI and locally. Set IQ_ENGINE_WIRE_ROOT when running the engine wire-parity node tests.
Cross-tenant deep links
¶ What the unit tests must assert
Deep links point at a workspace. Tests keep them pointing at the right one.
Triage/deep-link URLs include both the report id and the org id.
Rendered issue bodies contain the same parameters.
No hard-coded tenant ids.
Attachment URLs resolve in the correct workspace when the reader is a member.