mock_server | Mock HTTP interaction of Rack applications | Mock library

The root problem is that you're mocking the wrong things. If you have a file named ldapclient.py that contains your get_user_rest method, like this (note that I've rewritten things a bit to make our lives easier when writing tests):

Following the examples from the Postman documentation you mentioned - At Step 5 you should have a mock for the collection:

I've saved a simple GET request http://jsonplaceholder.typicode.com/users to the collection using the free jsonplaceholder API which will return details about users.

Once you have that response, hit the "Save Response" button and this will save that response as an example that can use with the mock server.

You can make requests against the mock server URL and add your route to the end of this in the Request Field. For me, it would look something like https://914aae16-28d5-47f1-8954-8a4d7b5e1daf.mock.pstmn.io/users

You just have to define initializationJson property specifying path to JSON file with expectations:

You may be using a major version of coverage which is incompatible with your version of pytest and/or pytest-cov. Make sure if you're using coverage 5.0, which was just released on December 14th, that you're also using the latest versions of these other modules.

Can you share your requirements.txt?

The key needs to be available for the remote_user on the target server running the task. By default it will read the default ssh keys available in ~/.ssh (e.g. id_rsa if you created an rsa one).

If the key is not in the default location/name, the git module has a key_file parameter you can use to point to the correct location.

You can either copy that key prior to running your playbook or in a task just before running git.

If you want to control everything from Jenkins, you could add the key content as a "secret file" credential in Jenkins, bind that credential to a var (which will contain the path to the secret temporary file), copy that file to the target server and use that uploaded file as the key (default or custom) in your ansible git task.

If you want to use properties in the version number of your project, you need you the ci-friendly properties (https://maven.apache.org/maven-ci-friendly.html). Other properties can only be used in dependencies, not in your own version number.

Currently, there is no way to turn off query param matching. If the query params do not match the algorithm falls back to match the path. The path matching is based on a fuzzy string matching algorithm which is why you are getting a response even though you were expecting a 404. One workaround for this is to save another example response for with a response code of 404 for my/api/path/endpoint and then send the x-mock-response-code header key with the value 404. This should return the example you have stored with the 404 status code.

Edit: the answer below is mostly irrelevant now – instead use pytest-trio and follow the instructions in its manual.

Your example pytest_pyfunc_call code doesn't work becaues it's a mix of trio and curio :-). For trio, there's a decorator trio.testing.trio_test that can be used to mark individual tests (like if you were using classic unittest or something), so the simplest way to write a pytest plugin function is to just apply this to each async test:

Ok, this is how I resolved this issue. I tried to run locally: