I am using pytest. I have two files in a directory. In one of the files there is a long running test case that generates some output. In the other file there is a test case that reads that output. How can I ensure the proper execution order of the two test cases? Is there any alternative other than puting the test cases in the same file in the proper order?
Answers:
Thank you for visiting the Q&A section on Magenaut. Please note that all the answers may not help you solve the issue immediately. So please treat them as advisements. If you found the post helpful (or not), leave a comment & I’ll get back to you as soon as possible.
Method 1
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 plugin for ordering tests: “pytest-ordering”. Check out the docs or install it from pypi. Right now I recommend using @pytest.mark.first and @pytest.mark.second, or one of the @pytest.mark.order# markers, but I have some ideas about more useful APIs. Suggestions welcome 🙂
Edit: pytest-ordering seems abandoned at the moment, you can also check out pytest-order (a fork of the original project by the author).
Edit2: In pytest-order, only one marker (order) is supported, and the mentioned examples would read @pytest.mark.order("first"), @pytest.mark.order("second"), or @pytest.mark.order(#) (with # being any number).
Method 2
Maybe you can consider using dependency pytest plugin, where you can set the test dependencies easily.
Be careful – the comments suggest this does not work for everyone.
@pytest.mark.dependency()
def test_long():
pass
@pytest.mark.dependency(depends=['test_long'])
def test_short():
pass
This way test_short will only execute if test_long is success and force the execution sequence as well.
Method 3
Pytest’s fixtures can be used to order tests in a similar way they order the creation of fixtures. While this is unconventional, it takes advantage of knowledge you may already have of the fixture system, it does not require a separate package and is unlikely to be altered by pytest plugins.
@pytest.fixture(scope='session')
def test_A():
pass
@pytest.mark.usefixtures('test_A')
def test_B():
pass
The scope prevents multiple calls to test_A if there are multiple tests that depend on it.
Method 4
There’s also a plugin pytest-ordering that seems to meet your requirements.
Method 5
Pytest by default, it’s executes the steps randomly. So use this option for executing in order.
Install with:
pip install pytest-order
Write the test method as like below:
import pytest
@pytest.mark.order(1)
def test_foo():
assert True
@pytest.mark.order(2)
def test_bar():
assert True
Method 6
It’s important to keep in mind, while trying to fix pytest ordering “issue”, that running tests in the same order as they are specified seems to be the default behavior of pytest.
It turns out that my tests were out of that order because of one of these packages – pytest-dependency, pytest-depends, pytest-order. Once I uninstalled them all with pip uninstall package_name, the problem was gone. Looks like they have side effects
Method 7
As indicated by @Frank T in the accepted answer, the pytest_collection_modifyitems hook hook allows to modify the order of collected tests (items) in place. This approach has the advantage of not requiring any third party library.
A full example on how to enforce test case execution order by test class is already available in this answer.
In this case, though, it seems like you would like to enforce execution order by test module (i.e., the .py file where the test lives). The following adaptation would allow you to do so:
# conftest.py
def pytest_collection_modifyitems(items):
"""Modifies test items in place to ensure test modules run in a given order."""
MODULE_ORDER = ["tests.test_b", "tests.test_c", "tests.test_a"]
module_mapping = {item: item.module.__name__ for item in items}
sorted_items = items.copy()
# Iteratively move tests of each module to the end of the test queue
for module in MODULE_ORDER:
sorted_items = [it for it in sorted_items if module_mapping[it] != module] + [
it for it in sorted_items if module_mapping[it] == module
]
items[:] = sorted_items
Placing the snippet above in conftest.py replaces the default alphabetical test execution order test_a -> test_b -> test_c with test_b -> test_c -> test_a. Modules can live in different test sub-directories, and the order of tests inside a module is left unchanged.
Method 8
main.py:
import functools
import pytest
from demo import test_foo,test_hi
def check_depends(depends):
try:
for dep in depends:
dep()
except Exception as e:
return dep
else:
return True
def pytest_depend(depends):
def pytest_depend_decorator(func):
stat = check_depends(depends)
if stat is True:
return func
else:
return pytest.mark.skip(True, reason="%s[skip] --> %s[Failed]" % (func.__name__, stat.__name__))(func)
return pytest_depend_decorator
@pytest_depend([test_foo,test_hi])
def test_bar():
pass
@pytest_depend([test_foo,test_hi])
def test_bar2():
pass
demo.py:
def test_hi():
pass
def test_foo():
assert False
platform linux — Python 3.5.2, pytest-3.8.2, py-1.6.0, pluggy-0.7.1 — /usr/bin/python3
pytest -vrsx ./plugin.py
Method 9
Make use of the ‘–randomly-dont-reorganize’ option or ‘-p no:randomly’ available in pytest-randomly plugin, this will just run your test in the same order as you mentioned in your module.
Module:
import pytest
def test_three():
assert True
def test_four():
assert True
def test_two():
assert True
def test_one():
assert True
Execution:
(tmp.w95BqE188N) <a href="https://getridbug.com/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="05776e6469646c76606973646b4561607328776e6469646c76606973646b">[email protected]</a>:~/$ py.test --randomly-dont-reorganize test_dumm.py ======================================================================== test session starts ======================================================================== platform linux2 -- Python 2.7.12, pytest-3.10.1, py-1.5.4, pluggy-0.7.1 -- /tmp/tmp.w95BqE188N/bin/python2 cachedir: .pytest_cache Using --randomly-seed=1566829391 rootdir: /home/rkalaiselvan, inifile: pytest.ini plugins: randomly-1.2.3, timeout-1.3.1, cov-2.6.0, mock-1.10.0, ordering-0.6 collected 4 items test_dumm.py::test_three PASSED test_dumm.py::test_four PASSED test_dumm.py::test_two PASSED test_dumm.py::test_one PASSED (tmp.w95BqE188N) <a href="https://getridbug.com/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="f4869f9598959d87919882959ab4909182d9869f9598959d87919882959a">[email protected]</a>:~/$ py.test -p no:randomly test_dumm.py ======================================================================== test session starts ======================================================================== platform linux2 -- Python 2.7.12, pytest-3.10.1, py-1.5.4, pluggy-0.7.1 -- /tmp/tmp.w95BqE188N/bin/python2 cachedir: .pytest_cache Using --randomly-seed=1566829391 rootdir: /home/rkalaiselvan, inifile: pytest.ini plugins: randomly-1.2.3, timeout-1.3.1, cov-2.6.0, mock-1.10.0, ordering-0.6 collected 4 items test_dumm.py::test_three PASSED test_dumm.py::test_four PASSED test_dumm.py::test_two PASSED test_dumm.py::test_one PASSED
Method 10
To me the simpliest way to fix tests execution order is to use them as fixtures, which are executed ordered by design.
@pytest.fixture()
def test_a():
print("running test a first")
pass
def test_b(test_a):
print("running test b after test a")
pass
Mark test dependency as fixture and pass it as an argument to dependent one.
Method 11
Make Sure you have installed pytest-ordering package.
To confirm go to Pycharm settings>>Project Interpreter >> and look for pytest-ordering :
If it is not available install it.
Pycharm settings>>Project Interpreter >> Click on + button and search pytest-ordering install it.
Voila!! It will definitely work.
All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0