When developing a dot net app, we make changes to the model regularly and may have our unit tests simply running of an in-memory, on the fly created database.
Everything could be working fine, all great, then we deploy, and suddenly everything stops working because we forgot that we needed to migrate the database.
How can I write a unit test that will fail if the model has changed yet it doesn't have a migration for that change?