First of all, what I want to accomplish here is to give you basic examples of how to mock data using two tools: mock and pytest monkeypatch.
Why bother mocking?
Some of the parts of our application may have dependencies for other libraries or objects. To isolate behaviour of our parts we need to substitue external dependencies. Here comes the mocking. We mock external API to have certain behaviours such as proper return values that we previously defined.
1 try: 2 import mock 3 except ImportError: 4 from unittest import mock 5 6 import unittest 7 8 from function import square, main 9 10 11 class TestNotMockedFunction(unittest.TestCase): 12 @mock.patch('__main__.square', return_value=1) 13 def test_function(self, mocked_square): 14 # because you need to patch in exact place where function that has to be mocked is called 15 self.assertEquals(square(5), 1) 16 17 @mock.patch('function.square') 18 @mock.patch('function.cube') 19 def test_main_function(self, mocked_square, mocked_cube): 20 # underling function are mocks so calling main(5) will return mock 21 mocked_square.return_value = 1 22 mocked_cube.return_value = 0 23 self.assertEquals(main(5), 1) 24 mocked_square.assert_called_once_with(5) 25 mocked_cube.assert_called_once_with(5) 26 27 if __name__ == '__main__': 28 unittest.main()
What is happening here? Lines 1-4 are for making this code compatible between python 2 and 3. In python 3 mock is part of standard library whereas in python 2 you need to install by pip install mock.
In line 13 I patched the square function. But you have to remember to patch it in the same place you use it. For instance, I’m calling square(5) in test itself so I need to patch it in __main__. This is the case if I’m running this by python tests/test_function.py. If I’m using pytest for that I need to patch it like test_function.square.
In lines 17-18, I patch square and cube functions in their module because they are used in main function. The last two asserts come from mock library and are for making sure that mock was called with proper values.
The same can be accomplished using mokeypatching for py.test:
As you can see I’m using monkeypatch.setattr for setting up return value for given functions. I’m still need to monkeypatch it in proper place: test_function_pytest and function.
Mocking classes
I have module called square:
1 2 3 4 5 6 7 8
import math
class Square(object): def __init__(radius): self.radius = radius
At line 13 I patch class Square (again be aware if you run this test using pytest or standard way). Lines 15 and 16 presents mocking instance; at first mocked_instance is mock object which by default returns another mock and to these mock.calculate_area I add return_value 1. In line 23 I’m using MagicMock which is normal mock class except it also retrieves magic methods from given object. Lastly I use patch.object to mock method in Square class.
The same using pytest:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
try: from mock import MagicMock except ImportError: from unittest.mock import MagicMock
The issue here is with test_mocking_class_methods which works well in python 3 but not in python 2. Right now I don’t have clear answer to this so if you can help I appreciate this!