2👍
After some re-googling (first attempt was several weeks ago and just couldn’t find this, because it appeared a month ago) I’ve found this topic, which leads me to django-test-utils; persistent database test runner (e.g. python manage.py quicktest) solves my case (in addition, it seems to be good app in general). In addition, I had to tweak TEST_DATABASE_NAME option in settings.py to my main database to fit my needs.
0👍
This doesn’t give you the behavior you’re asking for, just a potential alternate behavior:
While I deploy and run integration tests against my actual legacy database, I run unit tests against a SQLite database. It’s a small configuration change switching the DB engine to get it working. It ends up being faster and avoids clobbering any other work I’m doing.
- [Answered ]-Collectstatic throws 'OSError: [Errno 2] No such file or directory:' on dotcloud
- [Answered ]-How to run Django context processor
- [Answered ]-Nginx – permanent redirect to amazon s3 if one media file doesnot exist locally
- [Answered ]-Django custom authentication backend via third-party app
- [Answered ]-Django – custom filter not working properly