Fixed #11665 -- Made TestCase check deferrable constraints after each test.

2 files changed, 12 insertions, 1 deletions

diff --git a/docs/releases/1.10.txt b/docs/releases/1.10.txt
index db4f7d4632..b3bd4b8afd 100644
--- a/docs/releases/1.10.txt
+++ b/docs/releases/1.10.txt
@@ -333,7 +333,8 @@ Templates
 Tests
 ~~~~~
 
-* ...
+* To better catch bugs, :class:`~django.test.TestCase` now checks deferrable
+  database constraints at the end of each test.
 
 URLs
 ~~~~
@@ -541,6 +542,9 @@ Miscellaneous
   aggregate function now returns a ``float`` instead of ``decimal.Decimal``.
   (It's still wrapped in a measure of square meters.)
 
+* Tests that violate deferrable database constraints will now error when run on
+  a database that supports deferrable constraints.
+
 .. _deprecated-features-1.10:
 
 Features deprecated in 1.10
diff --git a/docs/topics/testing/tools.txt b/docs/topics/testing/tools.txt
index 5b8908c485..2bb53454cf 100644
--- a/docs/topics/testing/tools.txt
+++ b/docs/topics/testing/tools.txt
@@ -761,11 +761,18 @@ additions, including:
 * Wraps the tests within two nested ``atomic`` blocks: one for the whole class
   and one for each test.
 
+* Checks deferrable database constraints at the end of each test.
+
 * Creates a TestClient instance.
 
 * Django-specific assertions for testing for things like redirection and form
   errors.
 
+.. versionchanged:: 1.10
+
+    The check for deferrable database constraints at the end of each test was
+    added.
+
 .. classmethod:: TestCase.setUpTestData()
 
     The class-level ``atomic`` block described above allows the creation of