I have created a ticket on TRAC:
https://code.djangoproject.com/ticket/26659
If the ticket is accepted I'll push it as a pr.
Comments are welcome.
Regards,
Antonio
On 17/05/2016 21:31, Journeyman wrote:
On 17/05/2016 02:32, Josh Smeaton wrote:
I have the same problem when running tests in D
On 17/05/2016 02:32, Josh Smeaton wrote:
I have the same problem when running tests in Django's test suite. When
there's a failure, I have to copy the test path, paste that, then copy
the failing test.
Now that you mention it, another improvement could be to compose a
ready-to-copy-and-paste
On Tuesday, May 17, 2016 at 11:06:43 AM UTC+1, ludovic coues wrote:
>
> I might be saying something stupid, but rather than filtering test,
> would it not be better to have a flag to rerun all the test that
> failed in the previous run ?
>
>
That's why we extende DiscoverRunner to make
https:/
I might be saying something stupid, but rather than filtering test,
would it not be better to have a flag to rerun all the test that
failed in the previous run ?
So the command would always be the same for testA, testB or even both,
and might be more user-friendly if there is a bunch of test faili
Hi Antonio
I have the same problem when running tests in Django's test suite. When
there's a failure, I have to copy the test path, paste that, then copy the
failing test. The entire path to the test isn't printed in the failures.
I'd be a big fan of *some* kind of implementation that allows me
Hello everyone,
my name is Antonio, I'm using Django 1.9 and first of all I'd like to
thank you all contributors for the amazing framework I can work with.
I've just joined the django-dev mailing list to ask your opinion on a
really trivial patch I thought implementing.
Our backend server h
