Browse files

[1.3.X] Fixes #15595 -- emphasize the benefits of django.test.TestCas…

…e. Thanks for the patch Shawn Milochik

Backport of r16214 from trunk.

git-svn-id: bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
1 parent 5c08cda commit 9a4e5112b2384f1ec1db837b41d1ce9792143754 @SmileyChris SmileyChris committed May 11, 2011
Showing with 12 additions and 2 deletions.
  1. +12 −2 docs/topics/testing.txt
@@ -36,7 +36,8 @@ two test frameworks that ship in the Python standard library. The two
frameworks are:
* **Unit tests** -- tests that are expressed as methods on a Python class
- that subclasses ``unittest.TestCase``. For example::
+ that subclasses ``unittest.TestCase`` or Django's customized
+ :class:`TestCase`. For example::
import unittest
@@ -1102,7 +1103,16 @@ Converting a normal ``unittest.TestCase`` to a Django ``TestCase`` is easy:
just change the base class of your test from ``unittest.TestCase`` to
``django.test.TestCase``. All of the standard Python unit test functionality
will continue to be available, but it will be augmented with some useful
+additions, including:
+ * Automatic loading of fixtures.
+ * Wraps each test in a transaction.
+ * Creates a TestClient instance.
+ * Django-specific assertions for testing for things
+ like redirection and form errors.
.. class:: TransactionTestCase()

0 comments on commit 9a4e511

Please sign in to comment.