title: Why am I getting a 'ProgrammingError: relation "auth_user" does not exist' exception when running tests?
body: <p>Recently I've migrated a Django project from version 1.9.1 to 3.2.7.</p>
  <p>Now I'm trying to write some new tests, and I'm getting this error:</p>
  <pre><code># python manage.py test
  Creating test database for alias 'default'...
  Got an error creating the test database: database &quot;test_django&quot; already exists
  
  Type 'yes' if you would like to try deleting the test database 'test_django', or 'no' to cancel: yes
  Destroying old test database for alias 'default'...
  Traceback (most recent call last):
    File &quot;/opt/venv/lib/python3.6/site-packages/django/db/backends/utils.py&quot;, line 84, in _execute
      return self.cursor.execute(sql, params)
  psycopg2.errors.UndefinedTable: relation &quot;auth_user&quot; does not exist
  </code></pre>
  <p>I understand this is because currently I don't have any 'migrations' directory, as I cloned the git repo and the DB already existed when the Django project was running in version 1.9.1.</p>
  <p>I've read:</p>
  <ul>
  <li><a href="https://stackoverflow.com/questions/46726380/django-1-8-test-issue-programmingerror-relation-auth-user-does-not-exist">This question</a>.</li>
  <li><a href="https://stackoverflow.com/questions/50544714/auth-user-does-not-exist-when-doing-unit-testing-in-django">Also this one</a>.</li>
  <li><a href="https://stackoverflow.com/questions/30562754/django-1-8-programming-error-relation-auth-user-doesnt-exist-when-running-test">Also this</a>.</li>
  </ul>
  <p>All of them recommend running migrations, but:</p>
  <pre><code># python manage.py makemigrations 
  No changes detected
  # python manage.py makemigrations auth
  No changes detected in app 'auth'
  </code></pre>
  <p>Again, I think this is because the DB schema already existed before upgrading to 3.2.</p>
  <p>I cannot seem to solve the issue running the migrations approach.</p>
  <p>Is there another way to solve this issue, or force to generate the migrations even if the DB already exist and is synced (and possible fake them)?</p>