[1.4.X] Fixed #18057 - Documented that caches are not cleared after each test; thanks guettli for the suggestion.
Backport of 2aaa467a2a from master
This commit is contained in:
parent
1189dca471
commit
bd514f28e4
@ -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
|
the observed output of your code matches what will be seen in a production
|
||||||
setting.
|
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
|
Understanding the test output
|
||||||
-----------------------------
|
-----------------------------
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user