如何正确地对 Django 会话进行单元测试？
Django 会话的行为在“标准”视图代码和测试代码之间发生变化，这使得我们不清楚如何为会话编写测试代码。谷歌搜索得出关于此问题的两个相关讨论：
我很困惑，因为两张票都有不同的方式处理这个问题，而且它们都被接受了。我认为这意味着它们已被修补并且现在的行为有所不同。我也不知道这些补丁适用于哪些版本。
如果我在 Django 1.0 中编写单元测试，我将如何设置会话存储以使会话像在浏览器中一样工作？
The behavior of Django sessions changes between "standard" views code and test code, making it unclear how test code is written for sessions. Googling this yields two relevant discussions about this issue:
I'm confused because both tickets have different ways of dealing with this problem and they were both Accepted. I assume this means they were patched and the behavior is now different. I also don't know to which versions these patches would pertain.
If I'm writing a unit test in Django 1.0, how would I set up my session store for sessions to work as they do in the browser?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我不太明白你所说的“标准”视图和“测试”代码之间的行为变化是什么意思，也许你应该详细说明这一点。
但关于如何测试会话，我确实认为有一些方法。
因此您的问题看起来像是您在与服务器对话时没有传递登录回服务器时获得的 session_id 。就像把它放进去（POST、GET、COOKIES 我不太记得了）。
这里重要的是理解会话在 HTTP 中是如何工作的，一旦你明白了，你肯定对那里发生的事情有一个清晰的了解，并做出相应的解释。
I don't quite understand what do you mean by saying the behavior changes between "standard" view and "test" code, maybe you should elaborate on that.
but regarding how to test the session, I do think there are approaches.
so the issue for you looks like that you are not passing session_id you get when you log in back to server when you talk to server. like put it in (POST,GET,COOKIES I don't quite remember that ).
The important thing here is understand how session works in HTTP, once you get that, you definitely have a clear idea about what is happening there, and make explainations accordingly.