#27008: allow DEBUG to be enabled when running tests
-----------------------------------+--------------------------------------
Reporter: cjerdonek | Owner: nobody
Type: New feature | Status: new
Component: Testing framework | Version: 1.10
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+--------------------------------------
Changes (by timgraham):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
I'm not sure about this. While I've had this need from time to time, I've
found it easy enough to solve by temporarily adding an with `with
self.settings(DEBUG=True):` context manager to the test method in
question. Do you have a use case that involves debugging more than a
couple tests?
Setting `settings.DEBUG = True` in `setup_test_environment()` results in
70 failures/errors in Django's test suite. Adding an easy way to run the
test suite with that option leaves me wondering whether or not it would
become expected that everyone should aim to have their test suite passing
with both values of `DEBUG`.
--
Ticket URL: <https://code.djangoproject.com/ticket/27008#comment:1>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.1277cf33c9c2fb6127ac32389f0eb133%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
