Monday, August 29, 2016

1.7.9 deployment stubbornly won't create a test database

I've been handed a fairly large and built-up django 1.7.9 installation with several dozen pre-existing in-house modules and a lot of history. 

For some reason, any attempt to test  any of the existing modules runs tests against the live database specified in DATABASES['default'] rather than attempting to create a new test database.  I've written a couple of simple unit tests for a given module, generated a small fixture of data to apply to a blank schema for testing ... but I can't for the life of me find why this installation isn't creating a test_db. No errors, no failures ... just tests run against the production db.

Anyone have a pointer to what might be going on, or concepts to look up? A simple Hello World install using the same django version on the same machine works exactly as the docs suggest it should: I see 

Creating test database for alias 'default' (':memory:')...
Destroying test database for alias 'default' (':memory:')...

... but there are no such lines in my real installation.  I'm baffled.



You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
To post to this group, send email to
Visit this group at
To view this discussion on the web visit
For more options, visit

No comments:

Post a Comment