Open redbassett opened 9 years ago
I mean, I can easily just change the database connection URL to specify that the database should be on disk rather than in-memory, but it'll still get wiped on re-running our unit tests. I can see about getting the tests to connect to a completely different database instance, but that might take a little work.
Currently databases don't persist in test when the server is restarted. We absolutely need either a way to automate population of test data or (preferably) a way to persist data regardless of server status.