From 4d26f6512c82f258795953fae799efce3a79fac9 Mon Sep 17 00:00:00 2001 From: Chris Beaven Date: Wed, 11 May 2011 21:29:14 +0000 Subject: [PATCH] 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 --- docs/topics/testing.txt | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/docs/topics/testing.txt b/docs/topics/testing.txt index 91d37b1bf1..8e5cb9f954 100644 --- a/docs/topics/testing.txt +++ b/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. +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()