Thanks for the answer! Because i'm developing and integrating some flow (social registration etc) through tests.
So, instead of creating every time a new user, creating a new social association, and then after every try delete them from the database, the test does it from me. So, its like a kind of dirty TDD with functional (selenium because i have facebook login for example) testing. Anyway i think i can resolve with the 500 response logging the error to the console, but it's my first project in Django (and python) so i can't understand completely the way to logging at this moment. Alessandro Il giorno mercoledì 30 gennaio 2013 03:18:46 UTC+1, Ramiro Morales ha scritto: > > Ramiro Morales > On Jan 29, 2013 12:33 PM, "Alessandro Pelliciari" > <isac....@gmail.com<javascript:>> > wrote: > > > > thanks for the link! > > > > So Isn't there a way to set DEBUG=True in tests? > > No. There isn't (at least with the built-in testing toolbox). > > Now, I'm trying to understand why do you rely in the debugging 500 > response contents on your tests. Do you screen scrap it to extract > information about the origin of the failure? > -- 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.
