There is a bit of a dance to get this to work: activate your venv : source venv/bin/activate install pytest : pip install pytest re-activate your venv: deactivate && source venv/bin/activate The reason is that the path to pytest is set by the sourceing the activate file only after pytest is actually installed in the … Read more
For my situation, I found what the problem is: If there is –cov in pytest.ini, then breakpoints in pycharm won’t work, after deleting all –cov in pytest.ini, the breakpoints in pycharm can work. Reason: “The coverage module and pycharm’s debugger use the same tracing api (sys.settrace) – they don’t work together. ” — https://github.com/pytest-dev/pytest-cov/issues/131 References: … Read more
As you say yourself py.test basically assumes you have the PYTHONPATH setup up correctly. There are several ways of achieving this: Give your project a setup.py and use pip install -e . in a virtualenv for this project. This is probably the standard method. As a variation on this if you have a virtualenv but … Read more
The pytest docs for @pytest.fixture say this: If a fixture is used in the same module in which it is defined, the function name of the fixture will be shadowed by the function arg that requests the fixture; one way to resolve this is to name the decorated function fixture_<fixturename> and then use @pytest.fixture(name=”<fixturename>”). So … Read more
I spent ages trying to decipher this unhelpful error after creating a test that had import errors. Verify that your test suite can actually be executed before doing any deeper troubleshooting. pytest –collect-only is your friend.
I have fixed it by removing all __pycache__ pkg under test/ directory, the issue was when I was creating docker image its picking all my __pycache__ and *.pyc files too, at the time when test are running its using my local machine path instead of the path in docker container. Conclusion: Clear your *.pyc and … Read more
If you use py27+ or py32+, the solution is pretty simple: test_suite=”tests”,
In general you can configure the behavior of basically any part of pytest using its well-specified hooks. In your case, you want the “pytest_collection_modifyitems” hook, which lets you re-order collected tests in place. That said, it does seem like ordering your tests should be easier — this is Python after all! So I wrote a … Read more
I used to use Nose because it was the default with Pylons. I didn’t like it at all. It had configuration tendrils in multiple places, virtually everything seemed to be done with an underdocumented plugin which made it all even more indirect and confusing, and because it did unittest tests by default, it regularly broke … Read more
The documentation for py.test says that py.test implements the following standard test discovery: collection starts from the initial command line arguments which may be directories, filenames or test ids. recurse into directories, unless they match norecursedirs test_*.py or *_test.py files, imported by their package name. Test prefixed test classes (without an __init__ method) [<– notice … Read more