Autouse fixtures in PyTest

Introduction

Autouse fixtures run automatically without needing to be mentioned in tests. This helps set up or clean up things quietly behind the scenes.

When you want to prepare a database connection before every test without adding it to each test function.

When you need to reset some settings before each test automatically.

When you want to clean up temporary files after tests without calling cleanup explicitly.

When you want to apply a common setup step to many tests without changing their code.

Syntax

PyTest

import pytest

@pytest.fixture(autouse=True)
def setup_function():
    # setup code here
    yield
    # teardown code here

The autouse=True makes the fixture run automatically for all tests in the scope.

You don't need to add the fixture name to test function parameters.

Examples

This fixture prints messages before and after the test runs automatically.

PyTest

import pytest

@pytest.fixture(autouse=True)
def print_hello():
    print('Hello before test')
    yield
    print('Goodbye after test')

def test_example():
    print('Running test')

This fixture runs once before and after all tests in the module.

PyTest

import pytest

@pytest.fixture(autouse=True, scope='module')
def setup_module():
    print('Setup module')
    yield
    print('Teardown module')

def test_one():
    pass

def test_two():
    pass

Sample Program

This example shows an autouse fixture that runs setup and teardown prints automatically for each test.

PyTest

import pytest

@pytest.fixture(autouse=True)
def setup():
    print('Setup before test')
    yield
    print('Teardown after test')

def test_addition():
    assert 1 + 1 == 2

def test_subtraction():
    assert 5 - 3 == 2

Important Notes

Autouse fixtures can slow tests if they do heavy work and run too often.

You can control how often autouse fixtures run with the scope parameter (function, module, session).

Use autouse fixtures only when you want to avoid repeating fixture names in many tests.

Summary

Autouse fixtures run automatically for tests without being listed in test parameters.

They help with common setup and cleanup tasks across many tests.

Control their frequency with the scope option.