Testing and Quality¶
Existing evidence¶
The executor contains unit tests for config, dotenv handling, manifests, execution requests, network policy, metadata stores, runtime manager, session routes, and workspace sync. The frontend and executor expose TypeScript build/check scripts.
Quality matrix¶
| Boundary | Test focus |
|---|---|
| Job executor | limits, idempotent job IDs, failure flush, output metadata |
| Runtime manager | lease compatibility, dirty workspace, startup reconciliation |
| Storage | stage/persist/delete and MinIO/local parity |
| Metadata | SQLite/Postgres semantic parity |
| Security | restricted imports, network modes, ownership |
| Frontend | SSE chunk boundaries, event parsing, artifact viewers |
| Integration | upload → agent → executor → artifact → resume |
The biggest unverified quality gate is the planned LangGraph/backend/executor integration, because the product backend is not in the checkout.