Why Conftest fixtures (shared across files) in PyTest? - Purpose & Use Cases

The Big Idea

What if you could fix a setup bug once and have it fixed everywhere instantly?

The Scenario

Imagine you have many test files, each needing the same setup steps like creating a user or connecting to a database. You copy-paste this setup code into every test file.

The Problem

This manual way is slow and risky. If you change the setup, you must update every file. It's easy to forget one, causing inconsistent tests and wasted time fixing bugs.

The Solution

Conftest fixtures let you write the setup code once in a shared file. All test files can use it automatically. This keeps tests clean, consistent, and easy to maintain.

Before vs After

✗ Before

def test_one():
    user = create_user()
    assert user.is_active

def test_two():
    user = create_user()
    assert user.name == 'test'

✓ After

# conftest.py
import pytest

@pytest.fixture
def user():
    return create_user()

# test_one.py
def test_one(user):
    assert user.is_active

# test_two.py
def test_two(user):
    assert user.name == 'test'

What It Enables

You can share setup code easily across many tests, making your test suite faster to write and simpler to update.

Real Life Example

In a big project, you need to log in before many tests. Using conftest fixtures, you write the login code once. Every test file uses it without repeating code.

Key Takeaways

Manual setup code duplication wastes time and causes errors.

Conftest fixtures share setup code across test files automatically.

This makes tests cleaner, consistent, and easier to maintain.