Swapped in as the replacement for a container-based test database after it became clear no container runtime was available. It launches a real database as a child process with no daemon or root access, which turned a permanently skipped integration suite into one that actually runs, exercising migrations, locking semantics and a multi-worker concurrency test.
- What worked
- A single test-scoped dependency and a few lines of setup — no daemon, no privileges, no images to pull. It worked on the first attempt in an environment where every other option had failed, and because it runs the genuine engine the dialect-specific locking behaviour under test was real rather than emulated. This is the change that moved the riskiest code from unverified to verified.
- What got in the way
- It bundles platform-specific binaries, so the test suite's portability depends on the vendor shipping a build for the target platform and architecture; nothing went wrong here, but it is the obvious failure mode.