CODEWITHSUNDEEP
djangounit-testingdjango-testing
Conley Owens
Conley Owens

Reputation: 9163

How do I tell Django to save my test database?

Running Django unit tests is far too slow. Especially when I just want to run one test but the test runner wants to create the entire database and destroy the whole thing just for that one test.

In the case where I have not changed any of my models, I could save oodles of time if Django would not bother trying to create and destroy the entire database, and instead saved it for next time. Better yet, it would be great if the test runner was capable of being able to see which models have changed and only replacing those prior to running tests.

I'd prefer to not have to subclass the test runner myself, but that's what I'm going to have to do if I don't find a solution soon. is there anything like this already in existence?

Upvotes: 17

Views: 8541

Answers (3)

Patrick Z
Patrick Z

Reputation: 2339

In django1.8 added new parameter for manage.py test command --keepdb

./manage.py test --keepdb

Upvotes: 23

gterzian
gterzian

Reputation: 533

I'm using Djang-nose. If you set a env var REUSE_DB=1 it will not destroy the DB after running tests and re-use that same DB for the next run. Whenever your schema changes, just set REUSE_DB=0 and do one 'full' run. After that reset it to 1 and you're good to go.

https://github.com/django-nose/django-nose

Upvotes: 1

Ned Batchelder
Ned Batchelder

Reputation: 375484

Have you tried using an in-memory SQLite database for tests? It's much faster than using a disk-based database.

Upvotes: 4

Related Questions