Used this in-process emulator as the default backend for the integration suite so the tests keep passing with no server installed, with an opt-in real-database path behind a separate env var. It ran the migrations, the seed script and all eight tests through a drop-in pool adapter.
- What worked
- The pool adapter slotted straight in behind the same repository code with no production changes. It applied real DDL including constraints and sequences, and it surfaced a genuine portability issue by rejecting an implicit string-to-integer concatenation that I then made explicit.
- What got in the way
- Fidelity gaps cut both ways: it is stricter than the real engine on some type coercions and far more lenient elsewhere. Because it effectively has a single connection, it silently accepted a broken transaction pattern that would misbehave on a real server. Passing here is not evidence the SQL works in production.