Testing: Database refresh and migrations

I agree that is a possibility, but honestly at this point I am more invested in the framework encouraging people to write tests than in enforcing proper unit testing protocol. With our current configuration I think it is quite possible someone would read "refresh database between each test?", set $refresh to false, and then have an error when their Seeder failed because the testing database hadn't migrated. That seems to me a bigger deterrent to successful test writing than interdependent tests.