On Tue, Jan 6, 2009 at 9:25 PM, Todd O'Bryan wrote:
>
> On Tue, Jan 6, 2009 at 6:23 PM, Russell Keith-Magee
> wrote:
> > There are some plans in place to speed up test cases using
> > transactions; I'm hoping to be able to look at this once I put the
> > aggregation and F() code to bed, in the n
On Tue, Jan 6, 2009 at 6:23 PM, Russell Keith-Magee
wrote:
>
> On Wed, Jan 7, 2009 at 4:51 AM, Todd O'Bryan wrote:
>>
>> So, I've been trying to speed up tests. Surprise. I came across a
>> fairly easy solution, so I'm sure I must be missing something. If
>> someone could tell me what I'm missin
On Tue, Jan 6, 2009 at 6:05 PM, Malcolm Tredinnick
wrote:
>
> On Tue, 2009-01-06 at 14:51 -0500, Todd O'Bryan wrote:
> [...]
>
>> So, what am I missing? I know this doesn't deal with doctests--the db
>> gets cleaned for all of those, but does anyone see when this is just
>> going to blow up in my
On Wed, Jan 7, 2009 at 4:51 AM, Todd O'Bryan wrote:
>
> So, I've been trying to speed up tests. Surprise. I came across a
> fairly easy solution, so I'm sure I must be missing something. If
> someone could tell me what I'm missing, I'd really appreciate it.
...
> MyTestCaseSubclass.dirties_db = T
On Tue, 2009-01-06 at 14:51 -0500, Todd O'Bryan wrote:
[...]
> So, what am I missing? I know this doesn't deal with doctests--the db
> gets cleaned for all of those, but does anyone see when this is just
> going to blow up in my face?
For that to work reliably, you would need to deeply know the
So, I've been trying to speed up tests. Surprise. I came across a
fairly easy solution, so I'm sure I must be missing something. If
someone could tell me what I'm missing, I'd really appreciate it.
So, first I created my own subclass of django.test.TestCase:
class MyTestCase(django.test.TestCase
6 matches
Mail list logo
