Hi,
I am interested in it - could you be so nice and make this available anywhere?
Thanks a lot in advance.
TR
Am 17.01.2012 um 12:04 schrieb Thomas Guettler:
> Hi,
>
> same subject, but different content:
>
> we have a lot of tests which are read only. They don't modify the database or
> o
On Jan 20, 5:54 am, David Cramer wrote:
> So a few things we've done to take our test suite from 45 minutes to
> 12:
>
> 1. Implement global fixtures
>
> These get loaded after syncing just like initial data. Obviously this
> is a massive speed up
> as you only reload them in between transaction t
So a few things we've done to take our test suite from 45 minutes to
12:
1. Implement global fixtures
These get loaded after syncing just like initial data. Obviously this
is a massive speed up
as you only reload them in between transaction test cases.
2. Don't inherit from TestCase if you aren'
On Mon, Jan 16, 2012 at 10:46 AM, Anssi Kääriäinen
wrote:
> I have been investigating what takes time in Django's test runner and
> if there is anything to do about it. The short answer is: yes, there
> is a lot of room for improvement. I managed to reduce the running
> speed of the test suite (on
On 01/17/2012 01:04 PM, Thomas Guettler wrote:
Hi,
same subject, but different content:
we have a lot of tests which are read only. They don't modify the database or
other files.
You don't need to flush the database for every test of read only test cases.
These tests can be run on production
On 17 January 2012 12:04, Thomas Guettler wrote:
> Hi,
>
> same subject, but different content:
>
> we have a lot of tests which are read only. They don't modify the database
> or
> other files.
I assume your code has a way of checking that the tests are really
read only ? If yes, I would be inte
Hi,
same subject, but different content:
we have a lot of tests which are read only. They don't modify the database or
other files.
You don't need to flush the database for every test of read only test cases. These tests can be run on production
servers, too.
At the moment, this unittest cod
On Jan 16, 7:00 pm, Javier Guerra Giraldez wrote:
> On Mon, Jan 16, 2012 at 11:46 AM, Anssi Kääriäinen
>
> wrote:
> > I have been investigating what takes time in Django's test runner and
> > if there is anything to do about it. The short answer is: yes, there
> > is a lot of room for improvement
On Mon, Jan 16, 2012 at 11:46 AM, Anssi Kääriäinen
wrote:
> I have been investigating what takes time in Django's test runner and
> if there is anything to do about it. The short answer is: yes, there
> is a lot of room for improvement. I managed to reduce the running
> speed of the test suite (on
I have been investigating what takes time in Django's test runner and
if there is anything to do about it. The short answer is: yes, there
is a lot of room for improvement. I managed to reduce the running
speed of the test suite (on sqlite3) from 1700 seconds to around 500
seconds. On postgresql I
10 matches
Mail list logo
