From c17cd151d855ca1b8fcec894c5fccaa4a05be512 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Mon, 9 Jun 2014 12:09:16 -0400 Subject: Doc edits for refs #22487. --- docs/topics/testing/advanced.txt | 2 +- docs/topics/testing/overview.txt | 3 +-- 2 files changed, 2 insertions(+), 3 deletions(-) (limited to 'docs/topics/testing') diff --git a/docs/topics/testing/advanced.txt b/docs/topics/testing/advanced.txt index 8e9337b9b4..ac6e15557a 100644 --- a/docs/topics/testing/advanced.txt +++ b/docs/topics/testing/advanced.txt @@ -505,7 +505,7 @@ can be useful during testing. in-memory JSON string before running tests (used to restore the database state between tests if you don't have transactions). You can set this to False to significantly speed up creation time if you know you don't need - data persistance outside of test fixtures. + data persistence outside of test fixtures. ``keepdb`` determines if the test run should use an existing database, or create a new one. If ``True``, the existing diff --git a/docs/topics/testing/overview.txt b/docs/topics/testing/overview.txt index 026bbd8c88..3556cb1559 100644 --- a/docs/topics/testing/overview.txt +++ b/docs/topics/testing/overview.txt @@ -244,7 +244,7 @@ tests and not in ``TransactionTestCase`` tests, and additionally only on backends where transactions are supported (the most important exception being MyISAM). -Django can re-load that data for you on a per-testcase basis by +Django can reload that data for you on a per-testcase basis by setting the ``serialized_rollback`` option to ``True`` in the body of the ``TestCase`` or ``TransactionTestCase``, but note that this will slow down that test suite by approximately 3x. @@ -276,7 +276,6 @@ used. This behavior `may change`_ in the future. .. _may change: https://code.djangoproject.com/ticket/11505 - Understanding the test output ----------------------------- -- cgit v1.3