If you're not changing the schema, you could try using the "-k" option to keep the database between tests. This way it doesn't have to recreate it and the indexes each time you run your tests.
On Tuesday, 22 September 2015 11:22:51 UTC-6, Robert F. wrote: > > Does anyone have any strategies or techniques for running their unit tests > faster in Django 1.8? My project has seven model modules containing > twenty-one models (none of which are very complex). I run my tests using > the default Django test runner on a 1.86 GHz Mac laptop with 4 GB of RAM > against a local PostgreSQL 9.4.4 database. I'm finding that after > upgrading to Django 1.8, my test suite takes longer to start up (about > 10-11 seconds) than it takes to run the 180+ tests themselves (about 9 > seconds). I know one strategy would be to use SQLite for testing but I'd > prefer to run against my actual database server. I'm also using the > django-test-without-migrations > <https://pypi.python.org/pypi/django-test-without-migrations/> package to > avoid running migrations but that only speeds things up a little. Is there > anything else I can do? The longer startup time for tests in Django 1.8 > really makes it difficult to do true test-driven development. > > Thanks. > -- 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 django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/7b265e90-ca9f-43fe-8141-0155a790cfbb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
