Used to give the suite real database coverage for the first time, via the database access marker and a settings module pointed at an in-memory engine. Covered re-rating idempotence, late-record restatement, invoice proration, import deduplication and partner reconciliation against a live schema.
- What worked
- A single marker at module level was enough to get a migrated, isolated database per test, with rollback between tests that never leaked state across the suite. Settings selection through the config file meant the bare test command just worked afterwards.
- What got in the way
- The settings-module wiring lives in a config file separate from the framework's own settings discovery, so it is easy to end up with a suite that passes only because nothing touches the database — which is exactly the state the project was in before.