I have a method that accepts default arguments:
def build_url(endpoint, host=settings.DEFAULT_HOST):
return '{}{}'.format(host, endpoint)
I have a test case that exercises this method:
class BuildUrlTestCase(TestCase):
def test_build_url(self):
""" If host and endpoint are supplied result should be 'host/endpoint' """
result = build_url('/end', 'host')
expected = 'host/end'
self.assertEqual(result,expected)
@patch('myapp.settings')
def test_build_url_with_default(self, mock_settings):
""" If only endpoint is supplied should default to settings"""
mock_settings.DEFAULT_HOST = 'domain'
result = build_url('/end')
expected = 'domain/end'
self.assertEqual(result,expected)
If I drop a debug point in build_url
and inspect this attribute settings.DEFAULT_HOST
returns the mocked value. However the test continues to fail and the assertion indicates host
is assigned the value from my actual settings.py
. I know this is because the host
keyword argument is set at import time and my mock is not considered.
debugger
(Pdb) settings
<MagicMock name='settings' id='85761744'>
(Pdb) settings.DEFAULT_HOST
'domain'
(Pdb) host
'host-from-settings.com'
Is there a way to override this value at test time so that I can exercise the default path with a mocked settings
object?
Functions store their parameter default values in the func_defaults
attribute when the function is defined, so you can patch that. Something like
def test_build_url(self):
""" If only endpoint is supplied should default to settings"""
# Use `func_defaults` in Python2.x and `__defaults__` in Python3.x.
with patch.object(build_url, 'func_defaults', ('domain',)):
result = build_url('/end')
expected = 'domain/end'
self.assertEqual(result,expected)
I use patch.object
as a context manager rather than a decorator to avoid the unnecessary patch object being passed as an argument to test_build_url
.
这篇关于Python unittest mock:是否可以在测试时模拟方法默认参数的值?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持跟版网!