It looks like functools.wraps does not do the job well enough, so it breaks py.test’s introspection. Creating the decorator using the decorator package seems to do the trick. import decorator def deco(func): def wrapper(func, *args, **kwargs): return func(*args, **kwargs) return decorator.decorator(wrapper, func)
According to pytest documentation: unittest.TestCase methods cannot directly receive fixture function arguments as implementing that is likely to inflict on the ability to run general unittest.TestCase test suites.
@hynekcer gave me the right idea. But basically the easiest solution lies somewhere else: Get rid of pytest-cov! Use coverage run –source jedi -m py.test coverage report instead!!! This way you’re just running a coverage on your current py.test configuration, which works perfectly fine! It’s also philosophically the right way to go: Make each program … Read more
You can specify the tests to run by using the -k flag for filtering tests that match a string expression. When using parametrize, pytest names each test case with the following convention: test_name[‘-‘ separated test inputs] for example test_name[First_test_value-Second_test_value-N_test_value] Selecting an specific test to run is a matter of putting all the above together for … Read more
As of 2.5.0 py.test has the option –color=yes As of 2.7.0, it should be also possible to do: export PYTEST_ADDOPTS=”–color=yes”
You can use –dist=loadscope to group all the tests in the same test class. Here is the doc from pytest-xdist on pypi By default, the -n option will send pending tests to any worker that is available, without any guaranteed order, but you can control this with these options: –dist=loadscope: tests will be grouped by … Read more
There is a similar module that looks very mature: https://github.com/chmp/ipytest It is referenced in the module developed by @akaiola and is more active and regularly updated / maintained. Here is an example from the Github repository (https://github.com/chmp/ipytest/blob/master/Example.ipynb) And another one I have created recently
The easiest way to control the order in which fixtures are executed, is to just request the previous fixture in the later fixture. So to make sure b runs before a: @pytest.fixture(autouse=True, scope=”function”) def b(): pass @pytest.fixture(scope=”function”) def a(b): pass For details on the general fixture resolution order, see Maxim’s excellent answer below or have … Read more
As others already mentioned, you’d ideally write multiple tests and only have one assertion in each (that’s not a hard limit, but a good guideline). The @pytest.mark.parametrize decorator makes this easy: import pytest def parrot(i): return i @pytest.mark.parametrize(‘inp, expected’, [(0, 0), (1, 1), (2, 1), (2, 2)]) def test_parrot(inp, expected): assert parrot(inp) == expected When … Read more
All you need to do to test a class method is instantiate that class, and call the method on that instance: def test_action(self): sc = SuperCool() assert sc.action(1) == 1