概述
我正在尝试为在pathlib.Path上调用open方法的函数编写单元测试.我能够成功地模拟open方法而没有问题,但验证函数是否具有正确的行为是困难的.请参阅以下示例代码:
def test_my_function(self):
with patch.object(Path,'open') as mock_open:
my_function(*args) # This function calls Path.open
当我内省mock_open并查看_mock_mock_calls列表时,我无法找到正在写入的文件的字符串路径.通话记录如下所示:
[
call(mode='w'),call().__enter__(),call().__enter__().write('
有没有办法测试Path.open被调用时打开的路径?
使用函数模拟open(),返回mock_open()
object以进一步跟踪’打开文件’的使用,在Path实例上访问时将绑定函数:
from unittest.mock import patch,mock_open
def test_my_function(self):
opener = mock_open()
def mocked_open(self,*args,**kwargs):
return opener(self,**kwargs)
with patch.object(Path,'open',mocked_open):
my_function(*args) # This function calls Path.open
现在任何Path().open()调用都会调用opener mock,记录所有文件交互和调用它的Path()对象:
>>> from pathlib import Path
>>> from unittest.mock import patch,mock_open
>>> opener = mock_open()
>>> def mocked_open(self,**kwargs):
... return opener(self,**kwargs)
...
>>> with patch.object(Path,mocked_open):
... print(Path.open)
... print(Path().open)
... with Path().open() as f:
... f.write('
总结
以上是编程之家为你收集整理的python – 模拟/测试对Path.open的调用全部内容,希望文章能够帮你解决python – 模拟/测试对Path.open的调用所遇到的程序开发问题。
如果您也喜欢它,动动您的小指点个赞吧