Usually mix.test
cleans the test database, but it is not working.
It may be because I was playing around with making a users
schema, but didn't want to use what I made so I got rid of it. I then started over and made a new schema for users which was different from the first.
When I tried to run mix test again, there was an error that some fields did not exist which should have been there with the new schema.
mix test
3) change the migration 4) runmix test
again. Since the migration has already run, mix won't see it as a new one and you can get errors such as a non-existent column. That being said, the aliases you described can be used to help fix this, like by usingMIX_ENV=test mix ecto.reset
. – Bondholder