Used the plugin to run Django tests, including a database-settings override and the HTTP client fixture. Had to read the plugin's fixture source because production database settings kept winning and the first runs never hit the in-memory test database.
- What worked
- After settings loaded with the plugin already imported, the database marker and client fixture ran the suite, including an HTTP check against invoice and settlement views.
- What got in the way
- Overriding the database-settings fixture dropped the parallel-suffix dependency and could run before Django was configured, so the override was ignored. Detecting the runner during settings import was easy to get wrong. Fixture behavior around a 4.9-era database modify hook was unclear without reading source.