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

Used coverage module in documentation.

Browse Source
This commit is contained in:
Paolo Melchiorre 2024-10-23 22:35:50 +02:00
parent 4d11ea1ef0
commit 1e98c107fe
No known key found for this signature in database
GPG Key ID: 5F8222398E1ED035
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -375,19 +375,19 @@ To run coverage on the Django test suite using the standard test settings:
.. console::
$ coverage run ./runtests.py --settings=test_sqlite
$ python -m coverage run ./runtests.py --settings=test_sqlite
After running coverage, combine all coverage statistics by running:
.. console::
$ coverage combine
$ python -m coverage combine
After that generate the html report by running:
.. console::
$ coverage html
$ python -m coverage html
When running coverage for the Django tests, the included ``.coveragerc``
settings file defines ``coverage_html`` as the output directory for the report

4
docs/topics/testing/advanced.txt
View File

@ -867,14 +867,14 @@ following from your project folder containing ``manage.py``:
.. code-block:: shell
coverage run --source='.' manage.py test myapp
python -m coverage run --source='.' -m manage test myapp
This runs your tests and collects coverage data of the executed files in your
project. You can see a report of this data by typing following command:
.. code-block:: shell
coverage report
python -m coverage report
Note that some Django code was executed while running tests, but it is not
listed here because of the ``source`` flag passed to the previous command.