pytest Fixtures and Plugin Interoperability: Managing Session-Scoped State

Fixture Resolution and Teardown Logic

In pytest, naming conflicts between plugins and local configuration files are resolved via a hierarchical lookup. When a plugin and a local conftest.py both define a session-scoped fixture with the same name, the local conftest.py definition takes precedence. The local fixture overrides the plugin's version for all tests within that directory subtree and its descendants.

Regarding teardown, pytest utilizes a Last-In-First-Out (LIFO) sequence based on the dependency graph. If a session-scoped plugin fixture depends on a session-scoped local fixture, the local fixture is initialized first. Consequently, the plugin fixture is torn down before the local fixture is released.

Technical Explanation

Resolution Hierarchy

Pytest searches for fixtures in the following order of priority:

1. The test function/class itself.
2. The local conftest.py closest to the test file.
3. Parent conftest.py files moving up the directory tree.
4. Plugin-defined fixtures (built-in or third-party).

Because the local conftest.py is higher in the hierarchy than the plugin, it effectively masks the plugin's implementation. This can lead to state leakage or failures if the plugin's internal logic relies on the specific implementation of its own fixture.

Dependency Lifecycle

The teardown order is strictly the inverse of the setup order. For session-scoped resources:

• Setup: Local Fixture $\rightarrow$ Plugin Fixture (Dependent).
• Teardown: Plugin Fixture (Dependent) $\rightarrow$ Local Fixture.

Verification Steps

To verify the resolution and teardown behavior in your specific environment (assuming pytest 7.0+), use the following methods:

1. Inspect Fixture Source

Run the following command to see which fixture implementation is being used for a specific test module:

pytest --fixtures

2. Trace Execution Order

Implement yield fixtures with print statements to confirm the LIFO sequence:

# conftest.py (Local)
import pytest

@pytest.fixture(scope="session")
def shared_resource():
    print("\n[Setup] Local Resource")
    yield "local_val"
    print("\n[Teardown] Local Resource")

# plugin.py (Plugin)
@pytest.fixture(scope="session")
def plugin_resource(shared_resource):
    print("\n[Setup] Plugin Resource")
    yield "plugin_val"
    print("\n[Teardown] Plugin Resource")

Expected Output: Setup Local $\rightarrow$ Setup Plugin $\rightarrow$ Teardown Plugin $\rightarrow$ Teardown Local.

Note: To provide a more specific recommendation on state isolation, please clarify if you are using pytest_generate_tests for the parameterization of these session fixtures.