A massive problem that could occur was that we might deploy a version of the software with a migration that couldn't execute, in which case the website would be down(as the database would be in an unknown state while the app's code would expect the newest version. )
These tests are pretty crude, downloading the whole database. This is fine as long as the database is 200kb, but in a real situation you'd want to skim off a small subset of it to run these tests on.
A massive problem that could occur was that we might deploy a version of the software with a migration that couldn't execute, in which case the website would be down(as the database would be in an unknown state while the app's code would expect the newest version. )
These tests are pretty crude, downloading the whole database. This is fine as long as the database is 200kb, but in a real situation you'd want to skim off a small subset of it to run these tests on.