mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-08-31 07:47:37 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

Fixed #28478 -- Make DiscoverRunner skip creating unused test databases.

Browse source 
SimpleTestCase.databases makes it possible to determine the set of
databases required to run the discovered tests.
This commit is contained in:
Simon Charette 2018-07-12 00:14:24 -04:00 • committed by Tim Graham
parent 8c775391b7
commit 41e73de39d
8 changed files with 115 additions and 13 deletions
Download patch file Download diff file Expand all files Collapse all files

10
docs/topics/testing/advanced.txt
View file

@ -614,7 +614,7 @@ utility methods in the ``django.test.utils`` module.
Performs global post-test teardown, such as removing instrumentation from
the template system and restoring normal email services.
.. function:: setup_databases(verbosity, interactive, keepdb=False, debug_sql=False, parallel=0, **kwargs)
.. function:: setup_databases(verbosity, interactive, keepdb=False, debug_sql=False, parallel=0, aliases=None, **kwargs)
Creates the test databases.
@ -622,6 +622,14 @@ utility methods in the ``django.test.utils`` module.
that have been made. This data will be provided to the
:func:`teardown_databases` function at the conclusion of testing.
The ``aliases`` argument determines which :setting:`DATABASES` aliases test
databases should be setup for. If it's not provided, it defaults to all of
:setting:`DATABASES` aliases.
.. versionadded:: 2.2
The ``aliases`` argument was added.
.. function:: teardown_databases(old_config, parallel=0, keepdb=False)
Destroys the test databases, restoring pre-test conditions.

15
docs/topics/testing/tools.txt
View file

@ -1134,13 +1134,14 @@ Multi-database support
.. versionadded:: 2.2
Django sets up a test database corresponding to every database that is
defined in the :setting:`DATABASES` definition in your settings
file. However, a big part of the time taken to run a Django TestCase
is consumed by the call to ``flush`` that ensures that you have a
clean database at the start of each test run. If you have multiple
databases, multiple flushes are required (one for each database),
which can be a time consuming activity -- especially if your tests
don't need to test multi-database activity.
defined in the :setting:`DATABASES` definition in your settings and referred to
by at least one test through ``databases``.
However, a big part of the time taken to run a Django ``TestCase`` is consumed
by the call to ``flush`` that ensures that you have a clean database at the
start of each test run. If you have multiple databases, multiple flushes are
required (one for each database), which can be a time consuming activity --
especially if your tests don't need to test multi-database activity.
As an optimization, Django only flushes the ``default`` database at
the start of each test run. If your setup contains multiple databases,