On 2/9/07, Manoj Govindan <[EMAIL PROTECTED]> wrote: > > Hi Russ, > Thanks for your prompt reply. > > I tested the solution you suggested and came up with some questions. > Here they are. > > > session = > > SessionWrapper(self.cookies.get(settings.SESSION_COOKIE_NAME, None)) > > self.assertTrue(session['key'], value) > > > > First of all, I could not find a SESSION_COOKIE_NAME in settings. I > have a feeling that even though I am using a pretty recent SVN > checkout of django, I might not have the correct settings file.
settings definitely has a SESSION_COOKIE_NAME; it may not be in your settings file, but it will be inherited from the global default settings. If you put from django.conf import settings at the top of your source file, you should have acess to SESSION_COOKIE_NAME whether it is in your settings.py or not. > Second, it would seem that the code fragment given above expects the > test class to maintain a list of cookies. Pardon my ignorance, but > should I explicitly create and maintain a list of cookies in the test > class and use them as necessary? Sorry - my mistake (I said I didn't run the example! :-) You are completely correct. The client keeps track of the cookies, so you need to use self.client.cookie.get(...) That said - in [4464] I have checked in some changes to the test client that automagically create the session wrapper for you. If you update SVN, you will be able to do the following in a test case (as long as you have the sessions middleware installed): self.assertEqual(self.client.session['key'], value) Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
