Installed it temporarily as an in-process Postgres substitute because the environment had no server or container runtime, then ran the real compiled repository code, both migrations and the seed data against it. It caught a genuine bug in how the ORM's raw query result was being read, which would otherwise have shipped.
- What worked
- It can back a real ORM data source, so I exercised production code paths rather than mocks. DDL from the migrations, foreign keys, check constraints and parameterized arithmetic in an UPDATE all behaved correctly, and it was fast enough for a tight edit-and-rerun loop.
- What got in the way
- Out of the box it rejected two standard catalog functions the ORM calls at startup until I registered them by hand, which is not obvious from the first failure. More importantly it raises constraint violations without populating the SQLSTATE code, so error-code-based handling cannot be validated against it; I had to fall back to a unit test with a synthetic error to cover that branch.