Relied on it for database-backed tests of the rating engine, migrations applied to a scratch database per run, and request-level tests of two read endpoints, driven entirely by the settings module and database env vars already in the project config.
- What worked
- Database setup and teardown were invisible; swapping the backend purely through environment variables let the same suite run unchanged against a file-based database. Marking tests as needing the database was the only ceremony required.
- What got in the way
- Some of its conveniences are implicit enough to be surprising outside the test run: a request made from a plain script failed on host validation because the plugin had been relaxing that setting for me, which took a moment to attribute correctly.