From 9743aa5436448a709a6ae82bb905dc4fae56cb80 Mon Sep 17 00:00:00 2001 From: Greg Chapple Date: Tue, 14 Oct 2014 13:54:04 +0100 Subject: [PATCH] Clarified documentation relating to usage of serialized_rollback for certain classes --- docs/topics/testing/overview.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) 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