#8401: Default TEST_RUNNER - 'django.test.simple.run_tests' - forces
settings.DEBUG = False
---------------------------------------+------------------------------------
Reporter: rishi | Owner: nobody
Status: new | Milestone:
Component: Unit test system | Version: SVN
Resolution: | Keywords: TEST_RUNNER DEBUG test
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------+------------------------------------
Changes (by russellm):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
There are at least 2 very good reasons for forcing settings DEBUG=False
during tests. One is philosophical - your live site should be running with
Debug=False, and test conditions should be matching your live site. The
second reason is practial - there are some aspects of Django (most notably
the handling of errors in templates, but there are others) which can have
an effect on the output of tests.
If this isn't documented in the user docs, it should be. Documentation
changes are momentarily on hold until the documentation refactor lands in
a couple of days, but I'll look into this more when the refactor lands.
--
Ticket URL: <http://code.djangoproject.com/ticket/8401#comment:1>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
