p15693087
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Clarified documentation relating to usage of serialized_rollback for certain classes

This commit is contained in:
Greg Chapple 2014-10-14 13:54:04 +01:00 committed by Baptiste Mispelon
parent 7131efa154
commit 9743aa5436
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/topics/testing/overview.txt
View File

@ -242,7 +242,9 @@ Rollback emulation
Any initial data loaded in migrations will only be available in ``TestCase`` Any initial data loaded in migrations will only be available in ``TestCase``
tests and not in ``TransactionTestCase`` tests, and additionally only on tests and not in ``TransactionTestCase`` tests, and additionally only on
backends where transactions are supported (the most important exception being backends where transactions are supported (the most important exception being
MyISAM). MyISAM). This is also true for tests which rely on ``TransactionTestCase``
such as :class:`LiveServerTestCase` and
:class:`~django.contrib.staticfiles.testing.StaticLiveServerTestCase`.
Django can reload that data for you on a per-testcase basis by Django can reload that data for you on a per-testcase basis by
setting the ``serialized_rollback`` option to ``True`` in the body of the setting the ``serialized_rollback`` option to ``True`` in the body of the