On Sat, Oct 10, 2009 at 11:41 AM, Tim Chase <django.us...@tim.thechases.com>wrote:
> > Currently, I use > > t...@rubbish:~/django/trunk/tests$ python runtests.py > --settings=settings > > to execute the core set of tests. However, it takes quite a > while (on the order of hours) on my old box. Is there a way to > just run tests on the regressions/ subdirectory or even just a > particular file within? > > How do core devs typically make testing a subset faster? > > Hours? What database are you using? You show that you are running trunk level code, so you should have the transaction-based test speedup that went into 1.1. However, this speedup only helps for database configurations that support transactions, so if you are using MySQL with the MyISAM engine tests will run very slowly. If that is what is causing the slowness in your case, switching to using sqlite for the database for testing would help tremendously. On my oldest slowest machine (7 year old WinXP box with 384M of memory), current trunk tests take about 15 minutes to run using sqlite as the database. The 1.0.X branch, without the transaction speedups, takes 1.5 hours (even though it has 25% fewer tests). So the hours time you cite sounds to me like you must not be running a config that is using the test speedup that went into 1.1? Or do you really have a machine so much slower than my oldest? Karen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
