mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-10-23 21:59:11 +00:00
Code Issues 32 Releases Wiki Activity

Doc edits for refs #22487.

Browse Source
This commit is contained in:
Tim Graham
2014-06-09 12:09:16 -04:00
parent 4b25ebf112
commit c17cd151d8
6 changed files with 17 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/topics/testing/advanced.txt
View File

@@ -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

3
docs/topics/testing/overview.txt
View File

@@ -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
-----------------------------