From 21c82646fe3acf52251c1ecc618320657b97bd5e Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Mon, 16 Nov 2015 09:12:26 -0500 Subject: [PATCH] Documented how to see the full traceback of a test failure. --- .../contributing/writing-code/unit-tests.txt | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/docs/internals/contributing/writing-code/unit-tests.txt b/docs/internals/contributing/writing-code/unit-tests.txt index cfad2f1db6..cdf7960ac5 100644 --- a/docs/internals/contributing/writing-code/unit-tests.txt +++ b/docs/internals/contributing/writing-code/unit-tests.txt @@ -276,14 +276,21 @@ cause any trouble:: $ ./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 :ref:`SQL logging ` using the ``--debug-sql`` option. If you combine this with ``--verbosity=2``, all SQL queries will be output:: $ ./runtests.py basic --debug-sql -By default tests are run in parallel with one process per core. You can adjust -this behavior with the ``--parallel`` option:: +Seeing the full traceback of a test failure +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +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