Used database, settings, and HTTP client fixtures to test rating mediation and views without a live rater. Fixture sharing across modules was easy to get wrong, and it took a few attempts to mutate database settings in place instead of replacing the setup fixture and skipping migrations.
- What worked
- Once fixtures lived in the shared conftest, the built-in client and database marks were enough to cover commands, views, and model writes.
- What got in the way
- A plans fixture defined in one test module was not visible to another. Overriding the database setup fixture would have skipped migrations; the settings-mutation fixture had to be used instead, and its contract is easy to misread.