#14105: django.contrib.auth tests failing with cache middleware
-----------------------------------+----------------------------------------
Reporter: baumer1122 | Owner: PaulM
Status: assigned | Milestone:
Component: Contrib apps | Version: 1.2
Resolution: | Keywords:
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-----------------------------------+----------------------------------------
Comment (by christandiono):
Replying to [comment:4 toofishes]:
> * Always set CACHE_BACKEND to 'dummy://' when running tests- sucks if
you actually want to test caching concerns like making sure different
views go to different users even with caching enabled.
> * Set CACHE_BACKEND to 'dummy://' in supplied tests when we know we
want to examine context or templates in the response.
By the way, these don't seem to work, bizarrely enough. Our cache backend
has long been set to dummy because we've been too lazy to set it up,
although the two middlewares were still there (and causing tests to fail).
--
Ticket URL: <http://code.djangoproject.com/ticket/14105#comment:6>
Django <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 django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
