Skip to content

D
django
Kaydet (Commit) 21c82646 authored tarafından Tim Graham's avatar Tim Graham
Dosyalara gözat
Seçenekler

Documented how to see the full traceback of a test failure.

üst 1f8dad69
Show whitespace changes
Inline Side-by-side
Showing with 9 additions and 2 deletions
docs/internals/contributing/writing-code/unit-tests.txt
Dosyayı görüntüle @ 21c82646
...@@ -276,14 +276,21 @@ cause any trouble:: ...@@ -276,14 +276,21 @@ 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::
$ ./runtests.py basic --debug-sql $ ./runtests.py basic --debug-sql
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
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment