loop_scope="package" raises a fixture not found error

[NoahStapp]

When using loop_scope="package", this fixture defined in my test/asynchronous/conftest.py throws a fatal error on test setup:

@pytest_asyncio.fixture(loop_scope="package", scope="package", autouse=True)
async def test_setup_and_teardown():
    await async_setup()
    yield
    await async_teardown()

# Error:
E       fixture 'test/asynchronous::<event_loop>' not found

Every other loop_scope does not throw this error. Is there an additional step required for package scoped fixtures?

[seifertm]

@NoahStapp Thanks! This looks like a bug, indeed.

Can you also share the directory layout around the conftest, especially any init.py files?
My assumption is that autouse=True causes the fixture to be injected in tests that don't have a surrounding package.

[NoahStapp]

@NoahStapp Thanks! This looks like a bug, indeed.

Can you also share the directory layout around the conftest, especially any init.py files? My assumption is that autouse=True causes the fixture to be injected in tests that don't have a surrounding package.

Sure, here's the layout:

test
├── __init__.py
├── asynchronous
│   ├── __init__.py
│   ├── conftest.py
│   ├── # asynchronous test files...
├── conftest.py
├── # synchronous test files...

We use pytest-asyncio for our asynchronous test suite and pytest for our synchronous test suite.

[seifertm]

Slowly getting back to this…
I tried to reproduce the issue a few weeks ago, but I didn't have any success.

@NoahStapp Could you provide a minimal reproducible example that exhibits the error? For example, a bunch of files for me to copy to my development environment. This is the fastest way to get help.

[seifertm]

@NoahStapp The pytest-asyncio pre-release v1.0.0a1 introduces significant changes to the way scoped event loops are handled. Could you retest with pytest-asyncio==1.0.0a1 and see if this resolves the error?

[b-kamphorst]

I just bumped into the same issue (don't have a minimal example yet; fear it is quite some work to extract that), and the tests run fine with pytest-asyncio==1.0.0a1!

Edit: I experienced the issue with pytest-asyncio==0.26.0.

[seifertm]

Thanks @b-kamphorst !

Since this seems to be fixed with v1.0.0a1, let's close the issue. I'm happy to reopen, if there's any other indication.