title: Speeding up Django Testing
body: <p>Im looking to learn more about your testing flows with Django.</p>
  
  <p>Background information
  <a href="http://docs.djangoproject.com/en/dev/topics/testing/" rel="noreferrer">http://docs.djangoproject.com/en/dev/topics/testing/</a></p>
  
  <p>Im encountering difficulties when using test driven development.
  The test runner of Django constantly creates all db models in a test db when starting.
  For our current projects (between 40 and 240 models) this means it takes easily 20s for tests to start.</p>
  
  <p>This makes it completely unworkable for testing a new feature often.
  My question, how do you guys work around this?</p>
  
  <p>I've tried a few things in the past
  a.) - change the testloader to reuse the same test db every time and apply migrations when needed
  b.) - run my unit tests from within the <code>__main__</code> flow of python files</p>
  
  <p>option b is awkward with the sys.path, option a is doable but doesnt seem to be the django way.</p>
  
  <p>Update:
  Option A is indeed not such a bad solution. Its just quite a bit of effort. Which makes me believe people use a different workaround. SQL lite could be that workaround. But im guessing there are more.</p>