Why @pytest.fixture decorator? - Purpose & Use Cases

The Big Idea

What if you could write setup code once and have it magically ready for all your tests?

The Scenario

Imagine you have many tests that need the same setup, like creating a user account or connecting to a database. You write the setup steps inside each test manually.

The Problem

This manual way is slow and boring. If you want to change the setup, you must edit every test. It's easy to forget one and get wrong results. It also makes your test code messy and hard to read.

The Solution

The @pytest.fixture decorator lets you write the setup code once and share it with many tests. It runs the setup automatically before tests that need it, keeping your tests clean and easy to change.

Before vs After

✗ Before

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

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

✓ After

import pytest

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

def test_a(user):
    assert user.is_active

def test_b(user):
    assert user.name == 'test'

What It Enables

You can write simpler, cleaner tests that share setup code easily and stay correct even when things change.

Real Life Example

When testing a website, many tests need a logged-in user. Using @pytest.fixture, you create the user once and reuse it in all tests without repeating code.

Key Takeaways

Manual setup in each test is slow and error-prone.

@pytest.fixture shares setup code cleanly.

Tests become easier to write, read, and maintain.