Fixes #15595 -- emphasize the benefits of django.test.TestCase. Thanks for the patch Shawn Milochik

git-svn-id: http://code.djangoproject.com/svn/django/trunk@16214 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Chris Beaven 2011-05-11 21:29:14 +00:00
parent 73721912e2
commit 4d26f6512c
1 changed files with 12 additions and 2 deletions

View File

@ -36,7 +36,8 @@ two test frameworks that ship in the Python standard library. The two
frameworks are: frameworks are:
* **Unit tests** -- tests that are expressed as methods on a Python class * **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 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 just change the base class of your test from ``unittest.TestCase`` to
``django.test.TestCase``. All of the standard Python unit test functionality ``django.test.TestCase``. All of the standard Python unit test functionality
will continue to be available, but it will be augmented with some useful will continue to be available, but it will be augmented with some useful
additions. 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() .. class:: TransactionTestCase()