Patching target object with new argument results in error

Hello!

I’m trying to patch these three objects like that:

@asynctest.patch('foo.bar.method_1', new=asynctest.CoroutineMock)
@asynctest.patch('foo.bar.method_2', new=asynctest.CoroutineMock)
@asynctest.patch('foo.bar.method_3')
async def test_foo_bar(self, mock_method_3, method_2, method_1):

So I’m using the new argument because the library doesn’t properly identify the patched object (async def statement) as a coroutine. When running the tests I get the following error:

args = (<tests.unit_tests.test_app.test_foo_bar.TestRunFooBar testMethod=test_foo_bar>, <CoroutineMock name='method_3' id='140075174886144'>)
keywargs = {}
extra_args = [<CoroutineMock name='method_3' id='140075174886144'>]
patchers_to_exit = [<asynctest.mock._patch object at 0x7f65cbb5a080>]
patch_dict_with_limited_scope = []
exc_info = (<class 'TypeError'>, TypeError("test_foo_bar() missing 2 required positional arguments: 'method_2' and 'method_1'",), <traceback object at 0x7f65cb0a58c8>)
patching = <asynctest.mock._patch object at 0x7f65cbb5a080>
arg = <class 'asynctest.mock.CoroutineMock'>

[jeryini]

Great, thank you very much for explanation. I’m closing this issue now as I’ve resolved it.

[Martiusweb]

new allows to specify which object will replace the original patched object. if this parameter is not provided, the default behavior is to use a new instance of CoroutineMock or MagicMock (depending of whether the target of the patch is a coroutine function or not).

new_callable allows to specify a callable which returns the object that will replace the target of the patch. This one can be used to specify the type of the object that will replace the target, but it can be any kind of callable an can return something else than a mock.

I try to avoid repeating the documentation of unittest in asynctest’ documentation, but that’s true that this is far from obvious. I’ll rework the doc a bit.