I observed a similar issue and decided to see what’s going on exactly – let me describe my findings. I hope someone will find it useful. Short story It is indeed related to monkey-patching the threading module. In fact, I can easily trigger the exception by importing the threading module before monkey-patching threads. The following … Read more
I had a similar problem once, where I have to test configuration file against an expected file. That’s how I fixed it: Create a folder with the same name of your test module and at the same location. Put all your expected files inside that folder. test_foo/ expected_config_1.ini expected_config_2.ini test_foo.py Create a fixture responsible for … Read more
Recommended approach for pytest>=7: use the pythonpath setting Recently, pytest has added a new core plugin that supports sys.path modifications via the pythonpath configuration value. The solution is thus much simpler now and doesn’t require any workarounds anymore: pyproject.toml example: [tool.pytest.ini_options] pythonpath = [ “src” ] pytest.ini example: [pytest] pythonpath = src The path entries … Read more
To answer the question about the actual command (meaning the invocation of the tool on the command line) in a bit more detail: The py.test invocation is the old and busted joint. pytest is the new hotness (since 3.0). py.test and pytest invocations will coexist for a long time I guess, but at some point … Read more
One possible strategy is parameterizing the test in question, but not explicitly using the parameter. For example: @pytest.mark.parametrize(‘execution_number’, range(5)) def run_multiple_times(execution_number): assert True The above test should run five times. Check out the parametrization documentation: https://pytest.org/latest/parametrize.html
Putting an __init__.py is one way of resolving the conflict. Unlike nose, current pytest does not try to unload test modules in order to import test modules with the same import name. I used to think it’s a bit magic to do this auto-unimporting and might mess up people’s expectation from what the import mechanism … Read more
As The Compiler suggested, pytest has a new monkeypatch fixture for this. A monkeypatch object can alter an attribute in a class or a value in a dictionary, and then restore its original value at the end of the test. In this case, the built-in input function is a value of python’s __builtins__ dictionary, so … Read more
This issue seems to be fixed in pytest version 6.2.5. Please see: Fix assertion rewriting on Python 3.10
pytest seems to have the package attrs as a dependency. attrs==19.2.0 was released around 2019-10-01 17:00 UTC. This seems to cause the problem above. Switching back to attrs==19.1.0 fixes the problem. Just do the following: pip install attrs==19.1.0 NOTE: I expect that the issue will be resolved either by attrs or pytest soon by releasing … Read more
I don’t know why this didn’t work when I tried it before, but this solution works for me now: In test_module.py: import logging from module import run_function LOGGER = logging.getLogger(__name__) def test_func(caplog): LOGGER.info(‘Testing now.’) run_function() assert ‘Something bad happened!’ in caplog.text