#4457: Using a custom test suite, django.test.TestCase-based tests either fail
silently (DEBUG = True) or fail with a generic error message (DEBUG =
False)
------------------------------------------------+---------------------------
Reporter: Chris Wagner <[EMAIL PROTECTED]> | Owner:
russellm
Status: new | Component: Unit
test system
Version: SVN | Resolution:
Keywords: | Stage: Design
decision needed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
------------------------------------------------+---------------------------
Comment (by ubernostrum):
Replying to [comment:5 jacob]:
> I actually don't think this *is* a documentation issue. Under the built-
in test suite, a failing view called from a !TestClient will re-raise the
original exception (which is what Chris wants). I'm changing the component
back to unit tests so that Russ will see it.
OK. I still think there's a related documentation issue here (probably
worth a separate ticket, though) from the fact that we never warn people
that they'll need `500.html` and `404.html`; as soon as they flip DEBUG of
they'll start seeing `TemplateDoesNotExist` in places they never expected
it...
--
Ticket URL: <http://code.djangoproject.com/ticket/4457#comment:9>
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
-~----------~----~----~----~------~----~------~--~---
