嘲笑默认=时区。对于单元测试-Mockingdefault=timezone.nowforunittests

11  

I just ran into this issue myself. The problem is that models are loaded before mock has patched the timezone module, so at the time the expression default=timezone.now is evaluated, it sets the default kwarg to the real timezone.now function.

我自己也遇到了这个问题。问题是模型是在mock修补了时区模块之前加载的，所以在表达式default=timezone时。现在进行评估，它将默认的kwarg设置为真正的时区。现在的功能。

The solution is the following:

解决办法如下:

class MyModel(models.Model):
    timestamp = models.DateTimeField(default=lambda: timezone.now())

6  

Here's a method you can use that doesn't require altering your non-test code. Just patch the default attributes of the fields you want to affect. For example--

这里有一个不需要修改非测试代码的方法。只需修补您想要影响的字段的默认属性。例如——

field = User._meta.get_field('timestamp')
mock_now = lambda: datetime(2010, 1, 1)
with patch.object(field, 'default', new=mock_now):
    # Your code here

You can write helper functions to make this less verbose. For example, the following code--

您可以编写帮助函数来减少这种冗长。例如，下面的代码—

@contextmanager
def patch_field(cls, field_name, dt):
    field = cls._meta.get_field(field_name)
    mock_now = lambda: dt
    with patch.object(field, 'default', new=mock_now):
        yield

would let you write--

会让你写——

with patch_field(User, 'timestamp', dt):
    # Your code here

Similarly, you can write helper context managers to patch multiple fields at once.

类似地，您可以编写助手上下文管理器来一次修补多个字段。

0  

Looks like you are patching timezone in the wrong place.

看起来你是在错误的地方修补时区。

Assuming your User model lives in myapp\models.py and you want to test save() in that file. The problem is that when you from django.utils import timezone at the top, it imports it from django.utils. In your test you are patching timezone locally, and it has no effect on your test, since module myapp\models.py already has a reference to the real timezone and it looks like our patching had no effect.

假设您的用户模型生活在myapp\模型中。py需要在该文件中测试save()。问题是当你来自django的时候。在顶部的utils导入时区，它从django.utils导入。在您的测试中，您正在本地修补时区，它对您的测试没有影响，因为模块myapp\models。py已经提到了实际时区，看起来我们的补丁没有效果。

Try patching timezone from myapp\models.py, something like:

尝试从myapp\模型中修补时区。py,类似:

import myapp.models.timezone

def test_created(self):
    with patch('myapp.models.timezone') as mock_timezone:
        dt = datetime(2010, 1, 1, tzinfo=timezone.utc)
        mock_timezone.now.return_value = dt

        assert myapp.models.timezone.now() == dt

        user = User.objects.create(username='test')
        self.assertEquals(user.modified, dt)
        self.assertEquals(user.timestamp, dt)

0  

There is another easy way to do the above thing.

还有另一种简单的方法。

import myapp.models.timezone
from unittest.mock import patch

@patch('django.utils.timezone.now')
def test_created(self, mock_timezone):
    dt = datetime(2010, 1, 1, tzinfo=timezone.utc)
    mock_timezone.return_value = dt
    user = User.objects.create(username='test')

    self.assertEquals(user.modified, dt)
    self.assertEquals(user.timestamp, dt)

This is the best way to mock timezone.now.

这是模拟时间的最好方法。