summaryrefslogtreecommitdiff
path: root/docs/topics/testing/overview.txt
diff options
context:
space:
mode:
Diffstat (limited to 'docs/topics/testing/overview.txt')
-rw-r--r--docs/topics/testing/overview.txt23
1 files changed, 7 insertions, 16 deletions
diff --git a/docs/topics/testing/overview.txt b/docs/topics/testing/overview.txt
index fc18eb0e4a..06e6172724 100644
--- a/docs/topics/testing/overview.txt
+++ b/docs/topics/testing/overview.txt
@@ -135,13 +135,10 @@ 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.
+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 p to date.
By default the test databases get their names by prepending ``test_``
to the value of the :setting:`NAME` settings for the databases
@@ -173,10 +170,6 @@ If using a SQLite in-memory database with Python 3.4+ and SQLite 3.7.13+,
`shared cache <https://www.sqlite.org/sharedcache.html>`_ will be enabled, so
you can write tests with ability to share the database between threads.
-.. versionadded:: 1.8
-
- The ability to use SQLite with a shared cache as described above was added.
-
.. admonition:: Finding data from your production database when running tests?
If your code attempts to access the database when its modules are compiled,
@@ -218,11 +211,9 @@ the Django test runner reorders tests in the following way:
database by a given :class:`~django.test.TransactionTestCase` test, they
must be updated to be able to run independently.
-.. versionadded:: 1.8
-
- You may reverse the execution order inside groups by passing
- :djadminopt:`--reverse` to the test command. This can help with ensuring
- your tests are independent from each other.
+You may reverse the execution order inside groups by passing
+:djadminopt:`--reverse` to the test command. This can help with ensuring your
+tests are independent from each other.
.. _test-case-serialized-rollback: