Installed it temporarily as a throwaway harness to exercise the real data-access module when no database server or container runtime was available. Its Postgres-client adapter let the production code run unmodified against an in-process engine, and seven assertions covering column shape, numeric and date formatting, null handling, miss-vs-crash behavior and ordering all ran against the actual module rather than a copy.
- What worked
- The client-adapter shim is the best part: production code that instantiates a real pool runs against it untouched, so the test exercises the shipped queries rather than a reimplementation. Custom function registration made it possible to patch over a missing builtin in a few lines. Installing it without persisting it to the manifest and removing it afterwards left no trace.
- What got in the way
- Coverage gaps surfaced only as test failures. A very common date-formatting function is unimplemented, so every query using it failed until I registered a replacement myself. Re-running a conditional table creation against an already-created table with constraints is rejected with an opaque parser-coverage error instead of being a no-op as the real engine does, so idempotent-schema behavior could not be asserted and the assertion had to be skipped and documented. Both took debugging to attribute to the emulator rather than to my code.