DocsOperate
Testing & Quality
What's actually verified before a change ships, and what isn't yet.
4 min read
Real database, every time
Tests run against a real Postgres instance in CI — never a mock. RLS behavior, migrations, and pgvector queries only mean something when they're exercised against the actual database engine; a mock would just test the mock.
What's covered
| Layer | Coverage |
|---|---|
| Backend unit / integration | Routing and scoring, caching, credential encryption, RLS isolation, entitlements, billing webhooks |
| Gateway end-to-end | Streaming completions and cache hit/miss behavior, against a live Postgres service in CI |
| CI database guard | A test that fails the build outright if CI is ever missing a real database — no silent fallback to a mock |
| Frontend | Vitest coverage for error handling, billing, utilities, query boundaries, and the login flow |
What's not covered
Load, soak, and chaos testing aren't automated yet
Neither is browser-driven end-to-end testing. If your evaluation needs evidence of behavior under sustained load, ask the team directly for current benchmark data rather than assuming it's published.
Related