Used Django settings and the database fixture so rating tests could write catalog and usage rows. The first suite run failed because a shared catalog fixture did not request database access; adding the db fixture unblocked it.
- What worked
- Settings-module configuration and the db fixture were enough to run model-backed tests without a separate live database service.
- What got in the way
- Database access is not implied by Django settings alone; fixtures that touch models fail until they opt in, which cost an extra test cycle.