From 91e3d1215b081289f435e6ae1967ad85db2a9f52 Mon Sep 17 00:00:00 2001 From: David Gibbons Date: Wed, 16 Sep 2015 02:32:59 +0100 Subject: [PATCH] Updated docs coverage example to run in a single process. --- docs/internals/contributing/writing-code/unit-tests.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/internals/contributing/writing-code/unit-tests.txt b/docs/internals/contributing/writing-code/unit-tests.txt index 55e3a2d5c7..4acaa78c51 100644 --- a/docs/internals/contributing/writing-code/unit-tests.txt +++ b/docs/internals/contributing/writing-code/unit-tests.txt @@ -192,9 +192,10 @@ Contributors are encouraged to run coverage on the test suite to identify areas that need additional tests. The coverage tool installation and use is described in :ref:`testing code coverage`. -To run coverage on the Django test suite using the standard test settings:: +Coverage should be run in a single process to obtain accurate statistics. To +run coverage on the Django test suite using the standard test settings:: - $ coverage run ./runtests.py --settings=test_sqlite + $ coverage run ./runtests.py --settings=test_sqlite --parallel=1 After running coverage, generate the html report by running::