From b7aa7c4ab4372d2b7994d252c8bc87f77dd217ae Mon Sep 17 00:00:00 2001 From: Greg Chapple Date: Tue, 27 May 2014 22:13:08 +0100 Subject: Fixed #20550 -- Added ability to preserve test db between runs --- docs/topics/testing/overview.txt | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'docs/topics/testing') diff --git a/docs/topics/testing/overview.txt b/docs/topics/testing/overview.txt index 10dbc70f39..2d9808f0bc 100644 --- a/docs/topics/testing/overview.txt +++ b/docs/topics/testing/overview.txt @@ -149,6 +149,14 @@ Tests that require a database (namely, model tests) will not use your "real" Regardless of whether the tests pass or fail, the test databases are destroyed when all the tests have been executed. +.. versionadded:: 1.8 + + You can prevent the test databases from being destroyed by adding the + :djadminopt:`--keepdb` flag to the test command. This will preserve the test + database between runs. If the database does not exist, it will first + be created. Any migrations will also be applied in order to keep it + up to date. + By default the test databases get their names by prepending ``test_`` to the value of the :setting:`NAME` settings for the databases defined in :setting:`DATABASES`. When using the SQLite database engine -- cgit v1.3