Repository navigation
@pytest.mark.usefixtures take no effects on fixtures #378
Description
Originally reported by: BitBucket: oxyry, GitHub: oxyry
#!python
import pytest
@pytest.fixture
def app(scope='session'):
print('fixture.app')
@pytest.fixture
def client(app):
print('fixture.client')
@pytest.fixture
@pytest.mark.usefixtures('client')
def user_tom():
print('user jessie')
def test_a(user_tom):
print('test_a')
assert False
In above code, 'client' fixture does not run, but it runs if put 'client' into user_tom()'s args list.
Activity
pytestbot commentedon Nov 1, 2013
Original comment by holger krekel (BitBucket: hpk42, GitHub: hpk42):
usefixtures(and other markers likeparametrizefor that matter) are not advertised to work on fixture functions, only on test functions. I don't see the advantage of providingusefixtureson a fixture function, in particular.If you like to see marker support on fixture functions, please open an enhancement issue and provide some ideas/input on the semantics on that. thanks.
cjw296 commentedon Jan 10, 2025
I wonder if it might be time to re-open this since in the era of linters and type checkers, this becomes more of a problem.
In my case I have:
...which will upset linters because
sessionisn't used, but it is required for every downstream user of thesuperuser_headersfixture. Putting on the mark on every downstream user creates a lot of unnecessary text.I guess another option for an interface would be to allow something like:
Anyway, happy to open a new issue if that's better but this feels like the best one for now.