The mock_open() object does indeed not implement iteration. If you are not using the file object as a context manager, you could use: m = unittest.mock.MagicMock(name=”open”, spec=open) m.return_value = iter(self.TEST_TEXT) with unittest.mock.patch(‘builtins.open’, m): Now open() returns an iterator, something that can be directly iterated over just like a file object can be, and it’ll also … Read more
Everyone’s missing what’s probably the simplest and clearest solution: @patch(‘some.path’) def test(self, mock): f = asyncio.Future() f.set_result(‘whatever result you want’) process_smtp_message.return_value = f mock.assert_called_with(1, 2, 3) remember a coroutine can be thought of as just a function which is guaranteed to return a future which can, in turn be awaited.
You need to use return_value and PropertyMock: with patch(‘requests.post’) as patched_post: type(patched_post.return_value).ok = PropertyMock(return_value=True) This means: when calling requests.post, on the return value of that call, set a PropertyMock for the property ok to return the value True.
Try side_effect def my_side_effect(*args, **kwargs): if args[0] == 42: return “Called with 42” elif args[0] == 43: return “Called with 43” elif kwargs[‘foo’] == 7: return “Foo is seven” mockobj.mockmethod.side_effect = my_side_effect
You can assign an iterable to side_effect, and the mock will return the next value in the sequence each time it is called: >>> from unittest.mock import Mock >>> m = Mock() >>> m.side_effect = [‘foo’, ‘bar’, ‘baz’] >>> m() ‘foo’ >>> m() ‘bar’ >>> m() ‘baz’ Quoting the Mock() documentation: If side_effect is an … Read more
When you are using the patch decorator from the unittest.mock package you are patching it in the namespace that is under test (in this case app.mocking.get_user_name), not the namespace the function is imported from (in this case app.my_module.get_user_name). To do what you describe with @patch try something like the below: from mock import patch from … Read more