[Fixed]-How do I run Django tests on a copy of my production database?


Generally, testing against the live DB or a copy of the live DB is discouraged. Why? Because tests need to be predictable. When you make a copy of the live db, the input becomes unpredictable. The second problem is that you cannot obviously test on the live site, so you need to clone the data. That’s slow for anything more than few MB in size.

Even if the DB is small, dumpdata followed by loaddata isn’t the way. That’s because dumpdata by default exports in a JSON format which has a large generating overhead, not to mention making the data file very bulky. Importing using loaddata is even slower.

The only realistic way to make a clone is using the database engines built in export/import mechanism. In the case of sqlite that’s just copying the db file. For mysql it’s SELECT INTO OUTFILE followed by LOAD DATA INFILE. And for postgresql it’s COPY TO followed by COPY FROM and so on.

All of these export/import commands can be executed using the lowlevel connection object available in django and thus can be used to load fixtures.



You didn’t mention which version of Django you’re using, but looking at the 1.11 documentation:

It’s not clear from the 1.11 docs about fixture loading for tests whether they would also look in FIXTURE_DIRS, though. So this might not solve your problem entirely.

Leave a comment