Fixed #33213 -- Doc'd testing code coverage in parallel and used it.

This commit is contained in:
Paolo Melchiorre 2023-02-11 09:43:26 +01:00 committed by GitHub
parent b6ed389eec
commit 69352d85fa
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 12 additions and 5 deletions

2
.gitignore vendored
View File

@ -13,6 +13,6 @@ docs/_build/
docs/locale/
node_modules/
tests/coverage_html/
tests/.coverage
tests/.coverage*
build/
tests/report/

View File

@ -356,14 +356,19 @@ 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>`.
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:
To run coverage on the Django test suite using the standard test settings:
.. console::
$ coverage run ./runtests.py --settings=test_sqlite --parallel=1
$ coverage run ./runtests.py --settings=test_sqlite
After running coverage, generate the html report by running:
After running coverage, combine all coverage statistics by running:
.. console::
$ coverage combine
After that generate the html report by running:
.. console::

View File

@ -1,5 +1,7 @@
[run]
branch = True
concurrency = multiprocessing
data_file = .coverages/.coverage
omit =
*/django/utils/autoreload.py
source = django