#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:  
Accepted        
  Has_patch:  0                                 |           Needs_docs:  0      
         
Needs_tests:  0                                 |   Needs_better_patch:  0      
         
------------------------------------------------+---------------------------
Changes (by russellm):

  * stage:  Design decision needed => Accepted

Comment:

 Ok; found the problem. The issue is caused by not having a 500.html
 template. The template isn't actually used - the underlying exception is
 caught and rethrown, but the template must exist. If it doesn't exist, the
 request handler throws another exception, which is the error you are
 reporting. My test environment (and the Django test environment) both
 provide a 500.html template, so I didn't see the problem.
 
 Once I found the problem, the fix was pretty trivial. I just have to do
 some final testing; it should be in trunk shortly.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/4457#comment:12>
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to