The general development database has migrations applied manually, and they stay indefinitely, or at least till I make a goof and need to wipe the whole thing and start over. But the testing database is reused between apps and is much more volatile. So we need to be able to wipe and apply migrations automatically at the start of unit tests so the expected tables are available.
There was not too much too it, migrations are already isolated into a callable function (as wen we start doing server deployments, we need to also apply migrations there). But there was some other setup that I was avoiding that I was forced to do.
One was setting up nicer config files and loading them to get the database connection details. And the other was making sure the static data for the ORM was being correctly initialized.
Previous: Scroll + Selectables