Fixed #8401: Added a note on the fact that DEBUG=False is forced during test execution. Thanks to rishi for the suggestion.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@8514 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
6447582b85
commit
e822fd703b
|
@ -300,6 +300,14 @@ use the :setting:`TEST_DATABASE_COLLATION` setting to control the particular
|
||||||
collation used by the test database. See the :ref:`settings documentation
|
collation used by the test database. See the :ref:`settings documentation
|
||||||
<ref-settings>` for details of these advanced settings.
|
<ref-settings>` for details of these advanced settings.
|
||||||
|
|
||||||
|
Other test conditions
|
||||||
|
---------------------
|
||||||
|
|
||||||
|
Regardless of the value of the :setting:`DEBUG` setting in your configuration
|
||||||
|
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.
|
||||||
|
|
||||||
Understanding the test output
|
Understanding the test output
|
||||||
-----------------------------
|
-----------------------------
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue