I admit it is vexing that Django overrides what you have specified in
the settings file in this case, but it doesn't seem to be hard to
override. I simply added "settings.DEBUG = True" to the beginning of the
"setUp" function for the test class and that seems to do the trick.
Btw, I see tracebacks in the console when a page has errors while
running tests, don't you? Maybe that's a feature of django-nose, which I
am using, I don't know.
On Tuesday, January 29, 2013 2:39:58 AM UTC-6, Alessandro Pelliciari
wrote:
> When i run my selenium tests (LiveServerTestCase type) and i have some
> error in my code (not in the test, i mean in the code executed, like
> the homepage view i reach with selenium) i get the 500 public template
> (that usually i get when i have DEBUG = False) even if i have:
>
> DEBUG = True
> INTERNAL_IPS = ('127.0.0.1',)
>
>
> I'm stuck with that and i can't see why my test failed (because in the
> public 500 ofc i don't show the exceptions).
>
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
