diff options
| author | Tim Graham <timograham@gmail.com> | 2012-09-22 07:08:40 -0400 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2012-09-22 07:09:49 -0400 |
| commit | bd514f28e49887e8555c289546286dc27a17ddcc (patch) | |
| tree | b6812977dca79355bc181ae7d03a48744f80cafd /docs | |
| parent | 1189dca471b9d2c01a570526fbbcddf659dfff43 (diff) | |
[1.4.X] Fixed #18057 - Documented that caches are not cleared after each test; thanks guettli for the suggestion.
Backport of 2aaa467a2a from master
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/topics/testing.txt | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/docs/topics/testing.txt b/docs/topics/testing.txt index cd7ef9361f..ad4ef50550 100644 --- a/docs/topics/testing.txt +++ b/docs/topics/testing.txt @@ -494,6 +494,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 ----------------------------- |