mirror of
https://github.com/django/django.git
synced 2025-10-24 14:16:09 +00:00
@@ -504,12 +504,11 @@ can be useful during testing.
|
||||
* If autoclobber is ``True``, the database will be destroyed
|
||||
without consulting the user.
|
||||
|
||||
|
||||
``serialize`` determines if Django serializes the database into an
|
||||
in-memory JSON string before running tests (used to restore the database
|
||||
state between tests if you don't have transactions). You can set this to
|
||||
False to significantly speed up creation time if you know you don't need
|
||||
data persistance outside of test fixtures.
|
||||
data persistence outside of test fixtures.
|
||||
|
||||
Returns the name of the test database that it created.
|
||||
|
||||
@@ -517,6 +516,10 @@ can be useful during testing.
|
||||
:setting:`NAME` in :setting:`DATABASES` to match the name of the test
|
||||
database.
|
||||
|
||||
.. versionchanged:: 1.7
|
||||
|
||||
The ``serialize`` argument was added.
|
||||
|
||||
.. function:: destroy_test_db(old_database_name, [verbosity=1])
|
||||
|
||||
Destroys the database whose name is the value of :setting:`NAME` in
|
||||
|
||||
@@ -251,7 +251,7 @@ tests and not in ``TransactionTestCase`` tests, and additionally only on
|
||||
backends where transactions are supported (the most important exception being
|
||||
MyISAM).
|
||||
|
||||
Django can re-load that data for you on a per-testcase basis by
|
||||
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
|
||||
``TestCase`` or ``TransactionTestCase``, but note that this will slow down
|
||||
that test suite by approximately 3x.
|
||||
@@ -283,7 +283,6 @@ used. This behavior `may change`_ in the future.
|
||||
|
||||
.. _may change: https://code.djangoproject.com/ticket/11505
|
||||
|
||||
|
||||
Understanding the test output
|
||||
-----------------------------
|
||||
|
||||
|
||||
Reference in New Issue
Block a user