summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndrew Godwin <andrew@aeracode.org>2013-06-27 14:02:00 +0100
committerAndrew Godwin <andrew@aeracode.org>2013-06-27 14:02:00 +0100
commite26b589b8cd2c46c0e6af360abaacdb2fb0af27d (patch)
treee2309d4a61f4c2f07b8cade7ffd2386fb4cb0ebd
parentcab333cb16656cbb7d2bcfb06b2f7aeab9bac7af (diff)
Fixed #20590: Documented new test case ordering
-rw-r--r--docs/topics/testing/overview.txt10
1 files changed, 6 insertions, 4 deletions
diff --git a/docs/topics/testing/overview.txt b/docs/topics/testing/overview.txt
index 8268051a36..d56b1be20f 100644
--- a/docs/topics/testing/overview.txt
+++ b/docs/topics/testing/overview.txt
@@ -221,10 +221,12 @@ Order in which tests are executed
In order to guarantee that all ``TestCase`` code starts with a clean database,
the Django test runner reorders tests in the following way:
-* First, all unittests (including :class:`unittest.TestCase`,
- :class:`~django.test.SimpleTestCase`, :class:`~django.test.TestCase` and
- :class:`~django.test.TransactionTestCase`) are run with no particular ordering
- guaranteed nor enforced among them.
+* All :class:`~django.test.TestCase` subclasses are run first.
+
+* Then, all other unittests (including :class:`unittest.TestCase`,
+ :class:`~django.test.SimpleTestCase` and
+ :class:`~django.test.TransactionTestCase`) are run with no particular
+ ordering guaranteed nor enforced among them.
* Then any other tests (e.g. doctests) that may alter the database without
restoring it to its original state are run.