  ``'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 the tests within two nested ``atomic`` blocks: one for the whole class
    and one for each test.
  
  * Checks deferrable database constraints at the end of each test.
  
  * Creates a TestClient instance.
  
 
</s> remove Converting a normal :class:`unittest.TestCase` to a Django :class:`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:
 </s> add The class: </s> remove * Creates a TestClient instance.

* Django-specific assertions for testing for things like redirection and form
  errors.

 </s> add  </s> remove This class provides some additional capabilities that can be useful for testing
websites.
 </s> add This is the most common class to use for writing tests in Django. It inherits
from :class:`TransactionTestCase` (and by extension :class:`SimpleTestCase`).
If your Django application doesn't use a database, use :class:`SimpleTestCase`.
* Wraps the tests within two nested :func:`~django.db.transaction.atomic`
  blocks: one for the whole class and one for each test. Therefore, if you want
  to test some specific database transaction behavior, use
  :class:`TransactionTestCase`.
  ``'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:
  
* Wraps the tests within two nested :func:`~django.db.transaction.atomic`
  blocks: one for the whole class and one for each test. Therefore, if you want
  to test some specific database transaction behavior, use
  :class:`TransactionTestCase`.
* Wraps the tests within two nested :func:`~django.db.transaction.atomic`
  blocks: one for the whole class and one for each test. Therefore, if you want
  to test some specific database transaction behavior, use
  :class:`TransactionTestCase`.
* Wraps the tests within two nested :func:`~django.db.transaction.atomic`
  blocks: one for the whole class and one for each test. Therefore, if you want
  to test some specific database transaction behavior, use
  :class:`TransactionTestCase`.
* Wraps the tests within two nested :func:`~django.db.transaction.atomic`
  blocks: one for the whole class and one for each test. Therefore, if you want
  to test some specific database transaction behavior, use
  :class:`TransactionTestCase`.
  
  * Checks deferrable database constraints at the end of each test.
  
  * Creates a TestClient instance.
  
keep keep keep keep replace replace replace replace keep keep keep keep keep
 Refs #26270 -- Reorganized TestCase docs. 
docs/topics/testing/tools.txt