summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorTim Graham <timograham@gmail.com>2015-10-29 17:12:28 -0400
committerTim Graham <timograham@gmail.com>2015-11-07 20:33:49 +0100
commit1eb2ff3ff75b0f08276e0c3e10c99ed111572d8c (patch)
tree334030e899e6005c12beaea93685b692440b5e9d /docs
parent15377fceaa4aa28d15af22a63aebc35cb7fbbf87 (diff)
[1.9.x] Fixed #25290 -- Warned against modifying objects created in setUpTestData() in tests.
Backport of 81006b9657534a21c3eadb2bc4a87c46db54c099 from master
Diffstat (limited to 'docs')
-rw-r--r--docs/topics/testing/tools.txt6
1 files changed, 6 insertions, 0 deletions
diff --git a/docs/topics/testing/tools.txt b/docs/topics/testing/tools.txt
index 8c502d6c2e..f1667f757e 100644
--- a/docs/topics/testing/tools.txt
+++ b/docs/topics/testing/tools.txt
@@ -806,6 +806,12 @@ additions, including:
(for instance, MySQL with the MyISAM engine), ``setUpTestData()`` will be
called before each test, negating the speed benefits.
+ Be careful not to modify any objects created in ``setUpTestData()`` in
+ your test methods. Modifications to in-memory objects from setup work done
+ at the class level will persist between test methods. If you do need to
+ modify them, you could reload them in the ``setUp()`` method with
+ :meth:`~django.db.models.Model.refresh_from_db`, for example.
+
.. warning::
If you want to test some specific database transaction behavior, you should