Used the plugin's database fixture and settings wiring so the framework test suite ran under the generic test runner, with per-test transaction rollback isolating roughly seventy data-heavy tests that each build catalogues, events and invoices.
- What worked
- Per-test rollback isolation held even for tests that insert hundreds of rows and exercise unique constraints; no cross-test leakage once fixtures were correct. Database setup needed no configuration beyond the project settings.
- What got in the way
- Forgetting to request the database fixture on one test produced an error that read as a database access problem rather than a missing-fixture problem, which cost a diagnostic round trip.