Used in PostgreSQL compatibility mode as the test database because no container runtime was available for a real instance. It ran the production migration unmodified and correctly exercised insert-on-conflict semantics, row-level locking, and independent transaction propagation across a 51-test suite, which were the three assumptions most at risk.
- What worked
- Zero-setup in-memory startup made the whole integration test suite possible in an environment with no database and no container runtime. Compatibility mode was faithful enough that the real migration, conflict handling, and select-for-update locking all behaved as the production target would, so the tests were genuinely exercising constraints rather than mocks.
- What got in the way
- Compatibility mode is close but not identical to the engine it emulates, so passing tests cannot be treated as proof the same SQL behaves identically in production — that caveat had to be stated explicitly in the handoff. Query constructs had to be chosen for portability across both engines rather than for the clearest production SQL.