Test Django with error tracebacks

43 views
Skip to first unread message

Andrei

unread,
Nov 16, 2015, 9:12:52 AM11/16/15
to Django developers (Contributions to Django itself)
Hello,

I am(was) failing to find a way to enable error tracebacks e.g. in

$ runtests.py --failfast -v 3 migrations.test_writer

I see(saw) only 

test_nested_args_signature (migrations.test_writer.OperationWriterTests) ... ERROR

======================================================================
ERROR: test_nested_args_signature (migrations.test_writer.OperationWriterTests)
----------------------------------------------------------------------
ValueError: not enough values to unpack (expected 2, got 1)

----------------------------------------------------------------------
Ran 7 tests in 0.129s

and (since the django-dev chat does not respond...)  just got a reply so to be able to search 
for the answer in future here is how one does it these days here is the chat log:

[14:43] <highflux> hi, how does one get traceback in Django's tests? Sorry if I missed it in the docs but I did try :)
[14:44] <highflux> e.g. in `runtests.py --failfast -v 3 migrations.test_writer`
[14:49] <highflux> please?
[14:49] <highflux> err..sudo!
[14:55] <FunkyBob> highflux: they are just printed out after the run when I do it
[14:55] <highflux> eh
[14:55] <timograham> You need to add --parallel=1
[14:56] <highflux> ooo
[14:56] <highflux> yes!
[14:56] <highflux> thanks
[14:57] <highflux> maybe docs should mention it if it's a feature :D
[14:59] <timograham> sure, I'll propose a patch in a few minutes
[15:01] <highflux> thanks
[15:05] <+claudep> i'm just wondering if parallel=1 shouldn't be the default
[15:06] <+claudep> parallel>1 is mostly useful for ci robots
[15:06] <timograham> actually, we don't use it there because the jenkins test runner isn't compatible
[15:06] <timograham> I find it pretty useful for local development

Andrei
Reply all
Reply to author
Forward
0 new messages