Added it as a new test-scoped dependency so query construction could be exercised at build time without a real database. Declaring it is a one-liner with zero configuration, but it was never resolved or executed here, and it can only validate query wiring, not the production engine's behavior.
- What worked
- Single dependency line, no setup, and the framework autoconfigures an in-memory datasource for slice tests. The right weight of tool for checking that generated queries are structurally correct.
- What got in the way
- Dialect and optimizer differences mean passing tests say nothing about real access paths or index usage on the production engine, so I had to document that the real verification still has to happen elsewhere. Introducing a second database engine purely for tests is a known-false-confidence risk I had to call out rather than solve.