Relied on the database fixture and settings integration to write model-level tests for the new ledger, catalog and rating code. Once a usable database backend was selected it created and tore down test databases per run without issue.
- What worked
- The database fixture made transactional model tests trivial to write, and settings resolution from the project module needed no extra wiring. Test database creation and migration application were automatic.
- What got in the way
- When no database server was reachable, the failure surfaced as a connection error per test rather than a single clear 'no database configured' message, which made it slower than it should have been to work out that the inherited test setup had never been runnable in this environment.