Fixture are not meant to be called directly

[Overdrivr]

With pytest 4.1.0, it is no longer possible to pass a fixture to a parameterized test:

import pytest
from parameterized import parameterized

@pytest.fixture
def gen_test():
    return [('foo',), ('bar',)]

@parameterized(gen_test)
def test_(arg):
    print(arg)

Fixture "gen_test" called directly. Fixtures are not meant to be called directly,
but are created automatically when test functions request them as parameters.
See https://docs.pytest.org/en/latest/fixture.html for more information about fixtures, and
https://docs.pytest.org/en/latest/deprecations.html#calling-fixtures-directly about how to update your code.

Is there any workaround ? Ideally I would like to avoid passing a regular function (unless for some reason it's bad behavior) because my fixture is dependent on another fixture

[Overdrivr]

Any updates on this ? Using pytest major version 4 breaks builds instead of just raising a warning.
Related: pytest-dev/pytest#3950

[wolever]

Thanks for the report! I'll take a look into this when I get some cycles and report back. In the meantime, the larger issue with pytest 4 is here: #34

I'll post an update when I've figured out how to get this working.

[jatinp1]

Calling fixture directly feature is deprecated in 4.0 version. Install 3.10.0 version. It will work

[asher-dev]

I don't think there's an easy fix for this, but it can be done with a call to request.getfixturevalue(fixture_name) on the fixture request object (which is a parameter for fixtures) as long as there's a fixture context to call it from.

EDIT: I just looked again at what you're trying to do, and I think it will not be possible to use a fixture in this way with pytest 4. In order to parameterize the test, the parameters must be available outside of the test context -- but fixtures in pytest 4 cannot be run outside of a test context. If you need this to be a fixture because you use it as a fixture elsewhere, consider a layer of indirection (i.e. have the fixture call a non-fixture function that produces these values).

[wolever]

Hey folks - after consultation with @asher-dev, I don't believe this is a feature parameterized should support.

As mentioned, this appears to be an abuse (or, at least, misuse) of pytest fixtures as implemented in pytest4… so it might be possible to hack around, but I don't believe there's a strong usecase.

If you believe you have a usecase that is inline with "correct" pytest fixture usage, please comment here; I'm happy to reopen the issue if my understanding is faulty.