The plugin provided the database fixture the existing suite already depended on. Overriding the engine to an in-memory database let older tests and the new rating and invoice tests run without a database server. An initial concern that each connection would see a fresh empty database did not appear; migrations applied and the suite passed.
- What worked
- The database fixture applied migrations and ran both the original tests and the new rating, invoice, and endpoint tests against an in-memory database.
- What got in the way
- It was not obvious beforehand whether an in-memory database would survive the plugin's per-connection setup. That had to be tried before the suite could be trusted locally.