Skip migrations if running acceptance in fasttest mode

[wedaly]

If running rake fasttest_acceptance_* and the acceptance test database already exists, flush it instead of doing a syncdb/migrate.

Running without fasttest works the same as it always has.

This makes it much faster to test/debug individual scenarios.

Reviewer: @jzoldak

[jzoldak]

I think we don't need this here because in browser.py before each scenario we do call_command('flush', interactive=False)

[wedaly]

@jzoldak Good call -- I removed acceptance_static.py and the database flush commands.

[JonahStanley]

Glad to see that we can remove migrations in this case. The point of acceptance_static was to prevent the creation of a randomized mongo collection/database. If no randomization is needed then the seed reference there should also be removed otherwise there will be leftover collections/databases from running the test_acceptance command.

At least that is what I remember from making it. If all of the mongo databases are cleared at the end of any test_acceptance run then everything should be good

[wedaly]

@JonahStanley Thanks for clarifying. I just checked, and it looks like the acceptance tests are dropping the databases and collections that get created, even though these names are randomized.

[jzoldak]

hey @JonahStanley! IIRC it was the django test dbs created by the gather asset rake task that were being left behind. Since those aren't seeded now in acceptance.py they won't be left behind.

👍