summaryrefslogtreecommitdiff
path: root/docs/topics/testing.txt
diff options
context:
space:
mode:
authorKaren Tracey <kmtracey@gmail.com>2009-03-08 04:31:05 +0000
committerKaren Tracey <kmtracey@gmail.com>2009-03-08 04:31:05 +0000
commite8a817d499ac67ef936d47457916db1d6eba8582 (patch)
tree20a013d8410b29d3f46ce08077694294c3977411 /docs/topics/testing.txt
parentcd99c62e2de8701ffd940d86da8e41798c10007d (diff)
Fixed #10433: Corrected typo in test doc. Thanks Matt Doran.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@9989 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs/topics/testing.txt')
-rw-r--r--docs/topics/testing.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/topics/testing.txt b/docs/topics/testing.txt
index b7d04b4771..e4a514576f 100644
--- a/docs/topics/testing.txt
+++ b/docs/topics/testing.txt
@@ -830,7 +830,7 @@ behavior, you should use a Django ``TransactionTestCase``.
``TransactionTestCase`` and ``TestCase`` are identical except for the manner
in which the database is reset to a known state and the ability for test code
-to test the effects of commit and rollback. A ``TranscationTestCase`` resets
+to test the effects of commit and rollback. A ``TransactionTestCase`` resets
the database before the test runs by truncating all tables and reloading
initial data. A ``TransactionTestCase`` may call commit and rollback and
observe the effects of these calls on the database.