Eratothene wrote:
> I think you better not disable cache middleware in tests. If tests
> fail, so will be in production. I had similar problem, I thought it
> was something wrong with tests, but really it was problem in the code.
> My site was running well on django built-in server, but not on apache
> mod_python.
My site was working fine. My unittests was what were in error.
Yeah there are going to be differences between production and devel. But,
personally I
believe unittests should test one thing. Not many things at once such as
cache/view/db
(as an aside I'm sort of sad django doesn't have a mock db for view unittests)
So, I think you should test your cache framework and how your app uses it, but,
those
tests should not be part of the view unittests.
I was testing that a specific template was being used to render page. With
caching the
correct behavior is to not use any template, not to render at all, but rather
to pump
contents of cache down the wire.
In my test_settings.py file I have:
# disable cache for testing
MIDDLEWARE_CLASSES.remove('django.middleware.cache.CacheMiddleware')
CACHE_BACKEND = "dummy:///"
Then run
python manage.py --settings=test_settings test
works beautifully.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
