diff options
| author | Tim Graham <timograham@gmail.com> | 2015-10-29 17:12:28 -0400 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2015-11-07 20:27:46 +0100 |
| commit | 81006b9657534a21c3eadb2bc4a87c46db54c099 (patch) | |
| tree | f9f459e8aa1836f2eb59ec31eea868fb092f4d68 /docs | |
| parent | c3a974c81ec9d9b102cc9bd10c23e5579c751df1 (diff) | |
Fixed #25290 -- Warned against modifying objects created in setUpTestData() in tests.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/topics/testing/tools.txt | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/docs/topics/testing/tools.txt b/docs/topics/testing/tools.txt index ae5685b68d..ce23265351 100644 --- a/docs/topics/testing/tools.txt +++ b/docs/topics/testing/tools.txt @@ -787,6 +787,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 |
