p31829507
/
django
mirror of https://github.com/django/django.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

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

Thanks slinkp for the suggestion.

Backport of dd839a2dfd from master
This commit is contained in:
Tim Graham 2013-10-11 20:11:49 -04:00
parent 766fbd53cb
commit 2b8519760e
1 changed files with 9 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -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, can be certain that the outcome of a test will not be affected by another test,
or by the order of test execution. 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 URLconf configuration
~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~
@ -1351,6 +1355,11 @@ For example::
This test case will flush *all* the test databases before running This test case will flush *all* the test databases before running
``testIndexPageView``. ``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:
Overriding settings Overriding settings