summaryrefslogtreecommitdiff
path: root/docs/topics/testing/tools.txt
diff options
context:
space:
mode:
Diffstat (limited to 'docs/topics/testing/tools.txt')
-rw-r--r--docs/topics/testing/tools.txt12
1 files changed, 7 insertions, 5 deletions
diff --git a/docs/topics/testing/tools.txt b/docs/topics/testing/tools.txt
index b14a173987..eac4fa3ef7 100644
--- a/docs/topics/testing/tools.txt
+++ b/docs/topics/testing/tools.txt
@@ -873,11 +873,13 @@ It also provides an additional method:
(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.
+ .. versionchanged:: 3.2
+
+ Objects assigned to class attributes in ``setUpTestData()`` must
+ support creating deep copies with :py:func:`copy.deepcopy` in order to
+ isolate them from alterations performed by each test methods. In
+ previous versions of Django these objects were reused and changes made
+ to them were persisted between test methods.
.. _live-test-server: