mocker | Fluent mockito | Mock library

There are several solutions to this, the simplest is probably using a standard mock with a side effect:

There is not much benefit to mocking some_function1 as it does nothing but establish a connection to the database. It doesn't take any input and all it returns is a dictionary pointing at a table and a connection. With respect to some_function2 we can just pass in multiple MagicMock's inside the db_tools argument and use configure_mock.

Here is an improvised solution of https://stackoverflow.com/a/67498948/11043825 without using decorators.

As already pointed out, we still need to intercept the calls to the function that accepts the time argument which indicates how someApiCall would behave, which is either entry_point or someFunction. Here we would intercept someFunction.

Instead of implementing python decorator on someFunction which then needs to call that explicitly created decorated function, here we would amend (well this still follows the decorator design pattern) the someFunction in-place and make it available to the rest of the source code calls without explicitly changing the call to the decorated function. This is like an in-place replacement of the original functionalities, where we would replace (or rather wrap around) the original functionality with an updated one which would perform an assessment of the time before calling the original functionality.

Also for your reference, I solved it for 2 types of functions, a class method src.SomeClass.someFunction and a global function src.someFunction2.

./_main.py

Maybe something like this:

When you declare

You could try this:

What is happening here is that pytest internally uses a pathlib.Path object, which upon initialization asks for os.name to define which Path implementation to use. There are two internal implementations for Path, PosixPath and WindowsPath, which are only available under the respective systems. As you are faking a Posix system by patching os.name, it tries to instantiate a PosixPath object, which is not defined under Windows.

What you can do in this case is to wrap os.name in your own function, e.g. something like:

The stormssh module needs to be installed on the remote host on which the module is running, not on your local host where you're running the playbook. You may need an ansible task to install stormssh on your target hosts before the ssh_config task.

Possibly something like:

I tried to reproduce your problem and was unable to...

Here is the code I'm running: