Hacker News Reader

I've used django-test-migrations before and was really happy with it. https://pypi.org/project/django-test-migrations/

We've played around with that and it's on the roadmap. But it just adds another set of fixtures to herd.

What sort of proposal would you put forth? I generally install one of my production backups onto a staging server (secured appropriately for production data), and run the migrations against it to test.

That's not the intention on the code, I thought he is talking around writing a migration and a test that ensures the data migration is correctly applied

My strategy here is to have a staging server where migrations are applied before they can hit production.

As someone else pointed out, migration without CI can be dangerous and difficult to coordinate with deployment.

This is what we do but it's too manual for my taste.