Relied on the plugin to configure Django during tests so new model and invoice cases could use the database marker while older in-memory tests kept working. Needed an explicit test settings module because the project’s CI path did not start the production database.
- What worked
- Once settings pointed at a local test database, database-marked tests ran in the same suite as unsaved-model tests, and Django setup during collection did not become a blocker.
- What got in the way
- Default project settings were not enough; a separate test settings module had to be added so the plugin could run without the production database service.