diff options
| -rw-r--r-- | .gitignore | 2 | ||||
| -rw-r--r-- | docs/internals/contributing/writing-code/unit-tests.txt | 13 | ||||
| -rw-r--r-- | tests/.coveragerc | 2 |
3 files changed, 5 insertions, 12 deletions
diff --git a/.gitignore b/.gitignore index 6a67c6eb28..238fb3a200 100644 --- a/.gitignore +++ b/.gitignore @@ -13,6 +13,6 @@ docs/_build/ docs/locale/ node_modules/ tests/coverage_html/ -tests/.coverage* +tests/.coverage build/ tests/report/ diff --git a/docs/internals/contributing/writing-code/unit-tests.txt b/docs/internals/contributing/writing-code/unit-tests.txt index 40fb2ec221..634611dcfb 100644 --- a/docs/internals/contributing/writing-code/unit-tests.txt +++ b/docs/internals/contributing/writing-code/unit-tests.txt @@ -357,19 +357,14 @@ 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<topics-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: .. console:: - $ coverage run ./runtests.py --settings=test_sqlite + $ coverage run ./runtests.py --settings=test_sqlite --parallel=1 -After running coverage, combine all coverage statistics by running: - -.. console:: - - $ coverage combine - -After that generate the html report by running: +After running coverage, generate the html report by running: .. console:: diff --git a/tests/.coveragerc b/tests/.coveragerc index 258c82e8ee..e519f06259 100644 --- a/tests/.coveragerc +++ b/tests/.coveragerc @@ -1,7 +1,5 @@ [run] branch = True -concurrency = multiprocessing -data_file = .coverages/.coverage omit = */django/utils/autoreload.py source = django |