[1.5.x] Fixed #15582 -- Documented how TransactionTestCase.multi_db affects fixtures.

Thanks slinkp for the suggestion.

Backport of dd839a2dfd from master

1 files changed, 9 insertions, 0 deletions

diff --git a/docs/topics/testing/overview.txt b/docs/topics/testing/overview.txt
index ea475e0299..5982410205 100644
--- a/docs/topics/testing/overview.txt
+++ b/docs/topics/testing/overview.txt
@@ -1286,6 +1286,10 @@ This flush/load procedure is repeated for each test in the test case, so you
 can be certain that the outcome of a test will not be affected by another test,
 or by the order of test execution.
 
+By default, fixtures are only loaded into the ``default`` database. If you are
+using multiple databases and set :attr:`multi_db=True
+<TransactionTestCase.multi_db>`, fixtures will be loaded into all databases.
+
 URLconf configuration
 ~~~~~~~~~~~~~~~~~~~~~
 
@@ -1351,6 +1355,11 @@ For example::
 This test case will flush *all* the test databases before running
 ``testIndexPageView``.
 
+The ``multi_db`` flag also affects into which databases the
+attr:`TransactionTestCase.fixtures` are loaded. By default (when
+``multi_db=False``), fixtures are only loaded into the ``default`` database.
+If ``multi_db=True``, fixtures are loaded into all databases.
+
 .. _overriding-settings:
 
 Overriding settings