当你执行Parent.__init__ = Mock()时,你基本上重新定义了模块本身的__init__,然后反映在后面的测试中。
与其手动将Parent.__init__ 的实现更改为Mock,我的建议是使用unittest 和pytest-mock 中已有的修补功能。
src.py
class Parent:
def __init__(self, **kwargs):
print("Parent __init__ called")
class Child(Parent):
def __init__(self, **kwargs):
super().__init__(**kwargs)
print("Child __init__ called")
未经修正:
from unittest.mock import Mock, patch
from src import Child, Parent
def test_init_calls_real_parent_init():
Child()
def test_init_calls_updated_parent_init():
Parent.__init__ = Mock()
Child()
assert Parent.__init__.called
def test_init_calls_real_parent_init_2():
Child()
输出:
$ pytest -q test_src.py -rP
... [100%]
================================================================================================= PASSES ==================================================================================================
____________________________________________________________________________________ test_init_calls_real_parent_init _____________________________________________________________________________________
------------------------------------------------------------------------------------------ Captured stdout call -------------------------------------------------------------------------------------------
Parent __init__ called
Child __init__ called
___________________________________________________________________________________ test_init_calls_updated_parent_init ___________________________________________________________________________________
------------------------------------------------------------------------------------------ Captured stdout call -------------------------------------------------------------------------------------------
Child __init__ called
___________________________________________________________________________________ test_init_calls_real_parent_init_2 ____________________________________________________________________________________
------------------------------------------------------------------------------------------ Captured stdout call -------------------------------------------------------------------------------------------
Child __init__ called
3 passed in 0.01s
调查结果:
第一个测试称为真正的Parent.__init__。第二次测试称为模拟。然而在第三次测试中,它也意外地调用了第二次测试中的mock。
有修正:
from unittest.mock import Mock, patch
from src import Child, Parent
def test_init_calls_real_parent_init():
Child()
# Personally I wouldn't advise to do this. It just works :)
def test_init_calls_updated_parent_init():
# Setup
orig_parent_init = Parent.__init__ # Store original init
# Real test
Parent.__init__ = Mock()
Child()
assert Parent.__init__.called
# Teardown
Parent.__init__ = orig_parent_init # Bring back the original init
@patch("src.Parent.__init__") # Uses unittest
def test_init_calls_mocked_parent_init(mock_parent_init):
Child()
assert mock_parent_init.called
def test_init_calls_mocked_parent_init_2(mocker): # Uses pytest-mock
mock_parent_init = mocker.patch("src.Parent.__init__")
Child()
assert mock_parent_init.called
def test_init_calls_real_parent_init_2():
Child()
输出:
$ pytest -q test_src_2.py -rP
..... [100%]
================================================================================================= PASSES ==================================================================================================
____________________________________________________________________________________ test_init_calls_real_parent_init _____________________________________________________________________________________
------------------------------------------------------------------------------------------ Captured stdout call -------------------------------------------------------------------------------------------
Parent __init__ called
Child __init__ called
___________________________________________________________________________________ test_init_calls_updated_parent_init ___________________________________________________________________________________
------------------------------------------------------------------------------------------ Captured stdout call -------------------------------------------------------------------------------------------
Child __init__ called
___________________________________________________________________________________ test_init_calls_mocked_parent_init ____________________________________________________________________________________
------------------------------------------------------------------------------------------ Captured stdout call -------------------------------------------------------------------------------------------
Child __init__ called
__________________________________________________________________________________ test_init_calls_mocked_parent_init_2 ___________________________________________________________________________________
------------------------------------------------------------------------------------------ Captured stdout call -------------------------------------------------------------------------------------------
Child __init__ called
___________________________________________________________________________________ test_init_calls_real_parent_init_2 ____________________________________________________________________________________
------------------------------------------------------------------------------------------ Captured stdout call -------------------------------------------------------------------------------------------
Parent __init__ called
Child __init__ called
5 passed in 0.03s
调查结果:
这里我使用了 2 个解决方案:
- 在手动重新分配为 mock 后将
Parent.__init__ 的原始实现改回(请参阅 test_init_calls_updated_parent_init)(不建议)
- 或使用 unittest 和 pytest-mock 的内置修补功能(请参阅
test_init_calls_mocked_parent_init 和 test_init_calls_mocked_parent_init_2)
现在,第一个和最后一个测试都正确调用了实际的 Parent.__init__,即使在所有模拟完成之后也是如此。