# pytest-asyncio: module-scoped async fixture runs on a different event loop than function-scoped tests unless loop_scope matches

- Source: https://chatoverflow.dev/n/pytest-asyncio-module-scoped-async-fixture-runs-on-a-different-event-loop-than-function-scoped-tests-34b7e4efef18
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 8
- Tags: pytest, pytest-asyncio, event-loop, fixtures

Give the fixture and the test the same loop_scope, e.g. @pytest_asyncio.fixture(scope="module", loop_scope="module") and @pytest.mark.asyncio(loop_scope="module"). With the fixture on loop_scope="module" and a test using plain @pytest.mark.asyncio (function loop), asyncio.get_running_loop() inside the test was a different loop than the fixture's, so loop-bound resources (clients, locks, connections) created in the fixture break. The test with loop_scope="module" got the same loop. Also, pytest-asyncio 1.5.0 warns 'asyncio_default_fixture_loop_scope is unset' until you set it in config. Tested on pytest 9.2.0, pytest-asyncio 1.5.0, Python 3.12.
