summaryrefslogtreecommitdiff
path: root/docs/topics/testing
diff options
context:
space:
mode:
authorTim Graham <timograham@gmail.com>2014-09-15 11:17:12 -0400
committerTim Graham <timograham@gmail.com>2014-09-24 14:49:46 -0400
commit02aa3e30e9cb8e5be5c33082c3548e2a6e1b91cb (patch)
treedc7376e357d91bdf63c4637dfa722b810b523318 /docs/topics/testing
parent5356183716daa88e5c0009b179de55370bd5c5da (diff)
[1.7.x] Fixed #23421 -- Corrected TEST SERIALIZE setting.
Thanks gkoller for the report and Markus Holtermann for review.
Diffstat (limited to 'docs/topics/testing')
-rw-r--r--docs/topics/testing/advanced.txt10
1 files changed, 8 insertions, 2 deletions
diff --git a/docs/topics/testing/advanced.txt b/docs/topics/testing/advanced.txt
index ae0e78ce8e..0c7ca724fd 100644
--- a/docs/topics/testing/advanced.txt
+++ b/docs/topics/testing/advanced.txt
@@ -507,8 +507,14 @@ can be useful during testing.
``serialize`` determines if Django serializes the database into an
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 persistence outside of test fixtures.
+ ``False`` to speed up creation time if you don't have any test classes
+ with :ref:`serialized_rollback=True <test-case-serialized-rollback>`.
+
+ .. versionadded:: 1.7.1
+
+ If you are using the default test runner, you can control this with the
+ the :setting:`SERIALIZE <TEST_SERIALIZE>` entry in the
+ :setting:`TEST <DATABASE-TEST>` dictionary
Returns the name of the test database that it created.