Re: Application to update the Test Suite

On Sun, Apr 11, 2010 at 4:15 AM, Paul McMillan wrote: > Wow... lots of stuff here. > >> >> This is >> >> because SQLite uses an in-memory store, so it isn't disk bound; >> >> Postgres is disk bound, but is able to use transactions to optimize >> >> test setup and teardown; MySQL

Re: Application to update the Test Suite

Wow... lots of stuff here. > >> This is > >> because SQLite uses an in-memory store, so it isn't disk bound; > >> Postgres is disk bound, but is able to use transactions to optimize > >> test setup and teardown; MySQL is also disk bound, but doesn't support > >> transactions, so there are a lot

Re: Application to update the Test Suite

On Sat, Apr 10, 2010 at 2:25 PM, Alex Gaynor wrote: > On Sat, Apr 10, 2010 at 2:21 AM, Russell Keith-Magee > wrote: >> On Sat, Apr 10, 2010 at 8:29 AM, Gabriel Hurley wrote: >>> Maybe it's an overly simplistic question, but: what

Re: Application to update the Test Suite

On Sat, Apr 10, 2010 at 2:21 AM, Russell Keith-Magee wrote: > On Sat, Apr 10, 2010 at 8:29 AM, Gabriel Hurley wrote: >> Maybe it's an overly simplistic question, but: what makes the tests >> slow currently? It's not simply the volume of them. It's more

Re: Application to update the Test Suite

On Sat, Apr 10, 2010 at 8:29 AM, Gabriel Hurley wrote: > Maybe it's an overly simplistic question, but: what makes the tests > slow currently? It's not simply the volume of them. It's more than > possible for Python to race through hundreds of tests per second under > the right

Re: Application to update the Test Suite

On Fri, Apr 9, 2010 at 5:29 PM, Gabriel Hurley wrote: > Maybe it's an overly simplistic question, but: what makes the tests > slow currently? It's not simply the volume of them. It's more than > possible for Python to race through hundreds of tests per second under > the right

Re: Application to update the Test Suite

Maybe it's an overly simplistic question, but: what makes the tests slow currently? It's not simply the volume of them. It's more than possible for Python to race through hundreds of tests per second under the right conditions. Some of Django's test modules obviously zip along, but others seem to

Re: Application to update the Test Suite

I've revised the proposal, but am inlining more complete answers. > If someone needs to fix a bug, they will essentially need to > write the test twice; once for the old framework, and once for the > new. Do you have any suggestions on what we should be doing to > mitigate this complexity?

Re: [GSOC] Application to update the Test Suite

On Fri, Apr 9, 2010 at 8:59 AM, Paul McMillan wrote: > I've written an application to improve Django's Test Suite. > http://code.djangoproject.com/wiki/SummerOfCode2010#Testingupdates > > My application is here (also pasted below for convenience): >

[GSOC] Application to update the Test Suite

I've written an application to improve Django's Test Suite. http://code.djangoproject.com/wiki/SummerOfCode2010#Testingupdates My application is here (also pasted below for convenience): http://socghop.appspot.com/gsoc/student_proposal/show/google/gsoc2010/paulmcmillan/t127077396156 I'm hoping