mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2024-12-22 09:05:43 +00:00
Code Issues 25 Releases Wiki Activity

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

Browse Source 
This reverts commit 69352d85fa.

Test coverage for async methods was no longer calculated with this
change.
This commit is contained in:
Mariusz Felisiak 2023-03-15 13:05:48 +01:00 committed by GitHub
parent 8a844e761d
commit 78da5ca0c1
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 5 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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/

13
docs/internals/contributing/writing-code/unit-tests.txt
View File

@ -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::

2
tests/.coveragerc
View File

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