title: Disable migrations when running unit tests in Django 1.7
body: <p>Django <strong>1.7</strong> introduced <a href="https://docs.djangoproject.com/en/1.7/topics/migrations/" rel="noreferrer">database migrations</a>.</p>
  <p>When running the unit tests in Django 1.7, it forces a <em>migrate</em>, that takes a long time. So I would like to skip the django migrations, and create the database in the final state.</p>
  <p>I know that ignoring the migrations can be a bad practice, as that part of the code would not be tested. But that's not the case: I'm running the full migrations in the CI test server (jenkins). I only want to skip the migrations in my local tests, where the speed matters.</p>
  <hr />
  <p>Some context:</p>
  <p>Until Django <strong>1.6</strong>, when using South, I used the <a href="http://south.readthedocs.org/en/latest/unittests.html" rel="noreferrer"><em>SOUTH_TESTS_MIGRATE</em></a> setting:</p>
  <blockquote>
  <p>By default, South’s syncdb command will also apply migrations if it’s run in non-interactive mode, which includes when you’re running tests - it will run every migration every time you run your tests.</p>
  <p>If you want the test runner to use syncdb instead of migrate - for example, if your migrations are taking way too long to apply - simply set SOUTH_TESTS_MIGRATE = False in settings.py.</p>
  </blockquote>
  <p>However, <em>syncdb</em> does not exist anymore, now it's <em>migrate</em>.</p>
  <p>And from Django <strong>1.8</strong> I'll use the <em><a href="https://docs.djangoproject.com/en/dev/ref/django-admin/#django-admin-option---keepdb" rel="noreferrer">--keepdb</a></em> parameter:</p>
  <blockquote>
  <p>The --keepdb option can be used to preserve the test database between test runs. This has the advantage of skipping both the create and destroy actions which greatly decreases the time to run tests, especially those in a large test suite. If the test database does not exist, it will be created on the first run and then preserved for each subsequent run. Any unapplied migrations will also be applied to the test database before running the test suite.</p>
  </blockquote>
  <p>So this question is limited to Django 1.7.</p>