Question: Can someone explain the below uses of @pytest.mark.usefixtures

[thakkardharmik]

Question: Can someone explain the below two uses of @pytest.mark.usefixtures and how does each of them work. I would like to understand the difference in the marker and fixture definition/usage.

@pytest.fixture()
def populateList(f):
        assert 1 == 0

@pytest.mark.usefixtures(populateList)
def invokeFixture():
        pass

@pytest.fixture()
def populateList(f):
        assert 1 == 0

@pytest.mark.usefixtures("populateList")
def test_1():
        assert 0 == 0

[pytestbot]

GitMate.io thinks possibly related issues are #378 (@pytest.mark.usefixtures take no effects on fixtures), #121 (make pytest.mark available outside pytest), #2401 (pytest.mark not evaluated with pytest_generate_tests), #1111 (pytest.mark.parametrize fails with lambdas), and #666 (pytest.mark.skipif on class method uses "reason" from class level pytestmark).

[RonnyPfannschmidt]

1. is not supported
2. looks like a example that should work but breaks without more context

usefixtures uses the fixture names as strings

[thakkardharmik]

@RonnyPfannschmidt I see the usage of 1 in pytest doc.
https://docs.pytest.org/en/latest/usage.html#creating-junitxml-format-files

import pytest

@pytest.fixture(scope="session")
def log_global_env_facts(f):

    if pytest.config.pluginmanager.hasplugin('junitxml'):
        my_junit = getattr(pytest.config, '_xml', None)

    my_junit.add_global_property('ARCH', 'PPC')
    my_junit.add_global_property('STORAGE_TYPE', 'CEPH')

@pytest.mark.usefixtures(log_global_env_facts)
def start_and_prepare_env():
    pass

class TestMe(object):
    def test_foo(self):
        assert True

[RonnyPfannschmidt]

@thakkardharmik thanks for pointing that out, that seems like a mistake - to be specific that code is completely incorrect

[thakkardharmik]

@RonnyPfannschmidt though if I try to use similar idea in 1 it does work for me. Can you elaborate on what its trying to do there in scenario 1 though its not supported and how its working.

[RonnyPfannschmidt]

@tareqalayan the code paths im aware of support only function names there - if having a function there does actually have an effect thats an accident and should actually trigger an error

[thakkardharmik]

@RonnyPfannschmidt Thanks. Also you can see there is a slight change in fixture definition. When we pass function as an argument to usesfixture, the fixture too takes an parameter. I didnt quiet really understand what is happening there.

@pytest.fixture()
def populateList(f):
        assert 1 == 0

@pytest.mark.usefixtures(populateList)
def invokeFixture():
        pass

If we dont define 'f' as an parameter to the fixture it throws an error.

[RonnyPfannschmidt]

please show that error

[akr8986]

what is 'f' here ? is it the request object??

…

On 14 March 2018 at 15:56, Ronny Pfannschmidt ***@***.***> wrote: please show that error — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#3308 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AYTNhcMY8cTVINGkrDSKrZEQFI5rwIiuks5tePBggaJpZM4SqFcH> .

-- அன்புடன், பா. அருண் காளி ராசா

[tareqalayan]

@RonnyPfannschmidt yes it should be log_global_env_facts.name

[nicoddemus]

Fixed in #3309