Ticket #4501: 4501_v6.diff

docs/topics/testing.txt

@@ -553 +553 @@
 feature is useful if you're using the test-runner script in a shell script and
 need to test for success or failure at that level.
 
+Integration with coverage.py module
+-----------------------------------
+
+Code coverage describes how much source code have been tested. It indicates
+quality of your tests - the better code coverage is, the more lines are covered
+by tests and the better tests are. It's important part of testing applications,
+so it's strongly recommended to check coverage.
+
+Django can be easily integrated with `coverage.py module`_. First, you have to
+`install coverage.py`_. Now you are ready to use coverage module.
+When you are in your project folder, type in your shell:
+
+.. _coverage.py module: http://nedbatchelder.com/code/coverage/
+.. _install coverage.py: http://pypi.python.org/pypi/coverage
+
+.. code-block:: bash
+
+   coverage run --source='.' manage.py test myapp
+
+Now tests were launched and coverage data of all executed files in your project
+folder was collected. You can see a report by typing following command:
+
+.. code-block:: bash
+
+   coverage report
+
+Note that some of django code was executed during running tests, but
+it was not listed here because of flag ``source`` given to previous command.
+
+After this all don't forget to delete all collected data by typing:
+
+.. code-block:: bash
+
+   coverage erase
+
+Note that if you don't run last command, coverage data from next launching
+will be appended to existing data.
+
 Testing tools
 =============