Testing

Use this checklist to validate core features outside the automated suite.

What this page covers

Manual coverage for startup, auth, REST, search, tasks, CLI, MCP, migration, and backup.

Core workflow

1. Prerequisites:

• Docker + Docker Compose
• a reachable embedding provider: host Ollama with bge-m3, or a real OPENAI_API_KEY in .env
• Node 22+ only for the CLI or local-development checks
• gpg only for encrypted-backup checks

2. Baseline stack:

• clone the repository and choose the embedding provider before first start
• run docker compose up -d --build
• recover the one-time bootstrap token, create the first admin, and enroll MFA
• check /health; remember that this does not prove embedding reachability

3. Execute core test groups:

• Admin key creation and validation
• REST CRUD and stale-write conflict check
• Async enrichment + search after pending embedding work clears
• Task CRUD and completion
• CLI CRUD/task flows
• MCP tool list + store + search
• Talon dry-run then real migration
• Encrypted backup creation and restore sanity checks

4. Exit checks:

• health green
• CRUD and search successful
• queue operations stable
• latency and resource checks within targets

Notes

• Keep IDs returned by REST and CLI flows as variables for quick scripted reruns.
• When tests run in CI-like environments, prefer non-interactive flags and -T on docker exec calls.