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:34:07 +0100
commitbd55e8063544e0f7990bab7d9c981a6dc22c1654 (patch)
tree271468ca53f4d681ab124707669391f4b1f03679 /docs
parent189ceae19d81e5f01f5ba4d911087f7d5f2580a3 (diff)
[1.8.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 63e0df6c41..4b9671cb43 100644
--- a/docs/topics/testing/tools.txt
+++ b/docs/topics/testing/tools.txt
@@ -761,6 +761,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