e2a57414f4
As per: https://github.com/pytest-dev/pytest-mock#note-about-usage-as-context-manager pytest-mock is not meant to be used within a `with` context or as a decorator. Instead, pytest-mock will automatically unpatch the mocked methods when each test is complete. In newer pytest-mock, this use actually throws an exception and causes the tests to fail. This hasn't been hit in Ansible's CI yet, because the docker image that the tests run in uses an older version of pytest-mock. However, there is no constraint on the upper bound of pytest-mock in test/lib/ansible_test/_data/requirements/constraints.txt which means that when running the tests locally, outside of that docker image, the tests never pass. This patch removes the `with` context in each such case. Signed-off-by: Rick Elrod <rick@elrod.me> |
||
|---|---|---|
| .. | ||
| fixtures | ||
| __init__.py | ||
| test_avi.py | ||
| test_aws_secret.py | ||
| test_aws_ssm.py | ||
| test_conjur_variable.py | ||
| test_env.py | ||
| test_ini.py | ||
| test_laps_password.py | ||
| test_lastpass.py | ||
| test_manifold.py | ||
| test_onepassword.py | ||
| test_password.py | ||