p15693087
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

[1.9.x] Documented how to see the full traceback of a test failure. 

Backport of 21c82646fe from master
This commit is contained in:
Tim Graham 2015-11-16 09:12:26 -05:00
parent b3389956c9
commit 870914cb6c
1 changed files with 9 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/internals/contributing/writing-code/unit-tests.txt
View File

@ -276,6 +276,9 @@ cause any trouble::
$ ./runtests.py basic --reverse $ ./runtests.py basic --reverse
Seeing the SQL queries run during a test
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If you wish to examine the SQL being run in failing tests, you can turn on If you wish to examine the SQL being run in failing tests, you can turn on
:ref:`SQL logging <django-db-logger>` using the ``--debug-sql`` option. If you :ref:`SQL logging <django-db-logger>` using the ``--debug-sql`` option. If you
combine this with ``--verbosity=2``, all SQL queries will be output:: combine this with ``--verbosity=2``, all SQL queries will be output::
@ -286,8 +289,12 @@ combine this with ``--verbosity=2``, all SQL queries will be output::
The ``--reverse`` and ``--debug-sql`` options were added. The ``--reverse`` and ``--debug-sql`` options were added.
By default tests are run in parallel with one process per core. You can adjust Seeing the full traceback of a test failure
this behavior with the ``--parallel`` option:: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
By default tests are run in parallel with one process per core. When the tests
are run in parallel, however, you'll only see a truncated traceback for any
test failures. You can adjust this behavior with the ``--parallel`` option::
$ ./runtests.py basic --parallel=1 $ ./runtests.py basic --parallel=1