diff options
| author | Greg Chapple <gregchapple1@gmail.com> | 2014-10-14 13:54:04 +0100 |
|---|---|---|
| committer | Baptiste Mispelon <bmispelon@gmail.com> | 2014-10-14 17:13:37 +0100 |
| commit | 9743aa5436448a709a6ae82bb905dc4fae56cb80 (patch) | |
| tree | 2443c4fd4ee490fe838cd6e2a77ff85047757916 | |
| parent | 7131efa154a3e4dd0121503578fa6ca676366431 (diff) | |
Clarified documentation relating to usage of serialized_rollback for certain classes
| -rw-r--r-- | docs/topics/testing/overview.txt | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/docs/topics/testing/overview.txt b/docs/topics/testing/overview.txt index 3556cb1559..5104521f3b 100644 --- a/docs/topics/testing/overview.txt +++ b/docs/topics/testing/overview.txt @@ -242,7 +242,9 @@ Rollback emulation Any initial data loaded in migrations will only be available in ``TestCase`` tests and not in ``TransactionTestCase`` tests, and additionally only on 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 setting the ``serialized_rollback`` option to ``True`` in the body of the |