diff options
| author | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2023-03-15 13:05:48 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-03-15 13:05:48 +0100 |
| commit | 78da5ca0c1f2ab3201f8f6cd629e80d805ea023d (patch) | |
| tree | e993617bfb883630f825416bb280d19ebc9ad2b7 /docs/internals/contributing/writing-code/unit-tests.txt | |
| parent | 8a844e761d098d4005725f991a5e120a1f17cb70 (diff) | |
Reverted "Fixed #33213 -- Doc'd testing code coverage in parallel and used it."
This reverts commit 69352d85fa8412865db9e0c7f177b333c0eac3e2.
Test coverage for async methods was no longer calculated with this
change.
Diffstat (limited to 'docs/internals/contributing/writing-code/unit-tests.txt')
| -rw-r--r-- | docs/internals/contributing/writing-code/unit-tests.txt | 13 |
1 files changed, 4 insertions, 9 deletions
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:: |