Why advanced fixtures handle complex scenarios in PyTest - Automation Benefits in Action

Automate test setup using advanced pytest fixtures for complex scenario

Preconditions (2)

Step 1: Create an advanced fixture that sets up a database connection before tests and tears it down after tests

Step 2: Use the fixture in a test that inserts data into the database

Step 3: Verify the data insertion was successful

Step 4: Ensure the fixture handles setup and teardown only once for multiple tests

✅ Expected Result: Tests run successfully using the advanced fixture, data is inserted correctly, and setup/teardown happens only once

Automation Requirements - pytest

Assertions Needed:

Assert data inserted into database matches expected values

Assert fixture setup and teardown are called exactly once

Best Practices:

Use pytest fixtures with scope='module' or 'session' for complex setup

Use yield in fixtures to handle setup and teardown cleanly

Avoid hardcoding setup in each test, reuse fixture

Keep tests independent and idempotent

Automated Solution

PyTest

import pytest

class FakeDatabase:
    def __init__(self):
        self.data = []
        self.connected = False

    def connect(self):
        self.connected = True

    def disconnect(self):
        self.connected = False

    def insert(self, item):
        if not self.connected:
            raise Exception("Not connected")
        self.data.append(item)

    def get_all(self):
        return self.data

@pytest.fixture(scope="module")
def db():
    db_instance = FakeDatabase()
    db_instance.connect()  # Setup
    yield db_instance
    db_instance.disconnect()  # Teardown

def test_insert_data(db):
    db.insert({'id': 1, 'name': 'Test Item'})
    all_data = db.get_all()
    assert {'id': 1, 'name': 'Test Item'} in all_data

def test_insert_another_data(db):
    db.insert({'id': 2, 'name': 'Another Item'})
    all_data = db.get_all()
    assert {'id': 2, 'name': 'Another Item'} in all_data

This code defines a FakeDatabase class to simulate a database connection and data insertion.

The db fixture uses scope='module' so it sets up once per module, connecting before tests and disconnecting after all tests finish. The yield keyword separates setup and teardown.

Two tests use the db fixture to insert data and verify it was added correctly. Because the fixture is module-scoped, the database connection is reused, demonstrating how advanced fixtures handle complex setup and teardown efficiently.

Common Mistakes - 3 Pitfalls

Using function-scoped fixtures for expensive setup causing repeated setup/teardown

Not using yield in fixtures and manually calling teardown in tests

Hardcoding setup inside each test instead of using fixtures

Bonus Challenge

Now add data-driven testing with 3 different data inputs using the advanced fixture

Show Hint