From 2aaa467a2ab57d5616d384a70e2b6f8217ece63e Mon Sep 17 00:00:00 2001
From: Tim Graham <timograham@gmail.com>
Date: Sat, 22 Sep 2012 07:08:40 -0400
Subject: [PATCH] Fixed #18057 - Documented that caches are not cleared after
 each test; thanks guettli for the suggestion.

---
 docs/topics/testing.txt | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/docs/topics/testing.txt b/docs/topics/testing.txt
index 7afdbe88cc..117dfbe591 100644
--- a/docs/topics/testing.txt
+++ b/docs/topics/testing.txt
@@ -508,6 +508,13 @@ file, all Django tests run with :setting:`DEBUG`\=False. This is to ensure that
 the observed output of your code matches what will be seen in a production
 setting.
 
+Caches are not cleared after each test, and running "manage.py test fooapp" can
+insert data from the tests into the cache of a live system if you run your
+tests in production because, unlike databases, a separate "test cache" is not
+used. This behavior `may change`_ in the future.
+
+.. _may change: https://code.djangoproject.com/ticket/11505
+
 Understanding the test output
 -----------------------------