Browse files

[1.4.x] Fixed #4501 - Documented how to use with Django t…


Thanks krzysiumed for the draft patch.

Backport of 7ef2781 from master.
  • Loading branch information...
timgraham committed Oct 11, 2012
1 parent c06b724 commit 1be0515fe9940a7a727680a775395fe5f0c12b1d
Showing with 43 additions and 0 deletions.
  1. +43 −0 docs/topics/testing.txt
@@ -560,6 +560,49 @@ failed and erroneous tests. If all the tests pass, the return code is 0. This
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.
+Speeding up the tests
+In recent versions of Django, the default password hasher is rather slow by
+design. If during your tests you are authenticating many users, you may want
+to use a custom settings file and set the :setting:`PASSWORD_HASHERS` setting
+to a faster hashing algorithm::
+ 'django.contrib.auth.hashers.MD5PasswordHasher',
+ )
+Don't forget to also include in :setting:`PASSWORD_HASHERS` any hashing
+algorithm used in fixtures, if any.
+Integration with
+Code coverage describes how much source code has been tested. It shows which
+parts of your code are being exercised by tests and which are not. It's an
+important part of testing applications, so it's strongly recommended to check
+the coverage of your tests.
+Django can be easily integrated with ``_, a tool for measuring code
+coverage of Python programs. First, `install`_. Next, run the
+following from your project folder containing ````::
+ coverage run --source='.' 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::
+ 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.
+For more options like annotated HTML listings detailing missed lines, see the
+``_ docs.
+.. _install
Testing tools

0 comments on commit 1be0515

Please sign in to comment.