On Tue, Jan 19, 2010 at 12:39 AM, Eric Holscher wrote:
> Saw this go in, and it gets a huge +1 from me as well. However, I know that
> in the past we have talked about adding other things to the test runner
> (like coverage, etc), so it would seem like now would be a good time to
> recommend accep
Saw this go in, and it gets a huge +1 from me as well. However, I know that
in the past we have talked about adding other things to the test runner
(like coverage, etc), so it would seem like now would be a good time to
recommend accepting **kwargs in your custom test runners, so that when we
add i
On Sun, Jan 17, 2010 at 4:58 AM, Jeff Balogh wrote:
> On Sat, Jan 16, 2010 at 6:26 AM, Russell Keith-Magee
> wrote:
>> Hi all,
>>
>> This is a quick call for comment on ticket #12624.
>>
>> This ticket proposes to make Django's test runner a class-based,
>> rather than function based operation.
>
On Sat, Jan 16, 2010 at 6:26 AM, Russell Keith-Magee
wrote:
> Hi all,
>
> This is a quick call for comment on ticket #12624.
>
> This ticket proposes to make Django's test runner a class-based,
> rather than function based operation.
One thing:
http://docs.djangoproject.com/en/dev/releases/1.2/#
On Sat, Jan 16, 2010 at 8:26 AM, Russell Keith-Magee
wrote:
> Specifically, I want to make this change because I've had a couple of
> conversations in the recent past that have gone something like:
>
> Them: How do you make Django do X before/during/after a test run?
> Me: You write a custom tes
+1 for me, this will make my life a lot easier to implement a auto test
runner.
Is need to right up a proposal for change the code_change method a little,
but this is for another email.
Vitaly Babiy
On Sat, Jan 16, 2010 at 1:48 PM, Antoni Aloy wrote:
> +1 for me
>
> El 16/01/2010 15:26, "Russe
+1 for me
El 16/01/2010 15:26, "Russell Keith-Magee"
escribió:
Hi all,
This is a quick call for comment on ticket #12624.
This ticket proposes to make Django's test runner a class-based,
rather than function based operation.
This makes it much easier to modify the individual parts of the
beha
Hi all,
This is a quick call for comment on ticket #12624.
This ticket proposes to make Django's test runner a class-based,
rather than function based operation.
This makes it much easier to modify the individual parts of the
behavior of the Django test runner. For example if you want to:
- no
