Commit 9a4e5112 authored by Chris Beaven's avatar Chris Beaven
Browse files

[1.3.X] Fixes #15595 -- emphasize the benefits of django.test.TestCase. Thanks... 

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

Backport of r16214 from trunk.

git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.3.X@16215 bcc190cf-cafb-0310-a4f2-bffc1f526a37
parent 5c08cda6

docs/topics/testing.txt

+12 −2
Original line number Diff line number Diff line
@@ -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.

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()