each-cli-test-creates-isolated-db

IN premise

Every CLI test method initializes a fresh SQLite database via `run_cli("init")` in a pytest `tmp_path`, ensuring zero shared state between tests.

Summary

Each CLI test starts with its own temporary database, so no test can leak data into another. This isolation means test failures always point to the code under test rather than to ordering or shared-state bugs.

Dependents

These beliefs depend on this one:

cli-is-verified-end-to-end — The CLI is verified through hermetic end-to-end integration tests (isolated databases per test, full argv-parsing pipeline, deterministic stream-correct output) — unless cmd_propagate bypasses the API layer, leaving one code path's safety guarantees unverifiable through the standard integration testing harness.

Details

Source

entries/2026/04/29/tests-test_cli.md