Autouse fixtures in PyTest - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is an autouse fixture in pytest?

An autouse fixture is a pytest fixture that runs automatically for tests without needing to be explicitly requested. It helps set up or tear down test environments silently.

beginner

How do you declare a fixture as autouse in pytest?

You add the parameter autouse=True in the @pytest.fixture decorator. For example: @pytest.fixture(autouse=True).

intermediate

When should you use autouse fixtures?

Use autouse fixtures for setup or cleanup steps that every test needs, like resetting a database or configuring environment variables, so you don't have to add them to each test manually.

intermediate

Can autouse fixtures accept parameters?

Yes, autouse fixtures can accept parameters like any other fixture. They can also depend on other fixtures to build complex setups.

advanced

What is a potential downside of using autouse fixtures?

Autouse fixtures run for every test in their scope, which can slow down tests if the setup is heavy or unnecessary for some tests. It can also make tests less clear because the setup is hidden.

How do you make a pytest fixture run automatically for all tests without explicitly requesting it?

A Call the fixture inside each test

B Use @pytest.auto decorator

C Add autouse=True in the fixture decorator

D Name the fixture 'auto_fixture'

Adding autouse=True in the @pytest.fixture decorator makes the fixture run automatically for all tests in its scope.

What is the default scope of an autouse fixture if not specified?

A function

B module

C session

D class

By default, fixtures (including autouse) have function scope, meaning they run before each test function.

Which of the following is a good use case for autouse fixtures?

A Writing assertions inside tests

B Setting up a database connection for all tests

C Skipping tests conditionally

D Testing a single function's return value

Autouse fixtures are ideal for setup tasks needed by all tests, like database connections.

If an autouse fixture is slow, what is a likely impact?

A Tests run slower

B Tests run faster

C Tests skip the fixture

D Tests fail immediately

Since autouse fixtures run for every test, a slow fixture will slow down the entire test suite.

Can autouse fixtures be used with scopes other than 'function'?

A No, only function scope is allowed

B Only class scope is allowed

C Only session scope is allowed

D Yes, any scope like module or session

Autouse fixtures can have any scope: function, class, module, or session.

Explain what autouse fixtures are and how they help in pytest testing.

Think about how some setup steps should happen for every test without writing extra code.

Describe a scenario where using an autouse fixture might slow down your tests and how to avoid it.

Consider what happens if a slow setup runs before every test function.

Practice

1. What is the main purpose of an autouse fixture in pytest?

easy

A. To run the fixture automatically for all tests without explicitly adding it as a parameter

B. To skip the fixture during test execution

C. To run the fixture only when explicitly requested in the test

D. To disable all fixtures in the test file

Solution

1. Step 1: Understand what autouse means in pytest

   An autouse fixture runs automatically for every test in its scope without needing to be listed as a parameter.

2. Step 2: Compare options with this behavior

   Only To run the fixture automatically for all tests without explicitly adding it as a parameter describes this automatic running behavior correctly.

3. Final Answer:

   To run the fixture automatically for all tests without explicitly adding it as a parameter -> Option A

4. Quick Check:

   Autouse = automatic run without listing [OK]

Hint: Autouse means automatic use without listing in test [OK]

Common Mistakes:

• Thinking autouse disables the fixture
• Believing autouse requires explicit test parameters
• Confusing autouse with skipping tests

2. Which of the following is the correct way to declare an autouse fixture in pytest?

easy

A. @pytest.fixture(auto=True)
def setup():
pass

B. @pytest.fixture(autouse=True)
def setup():
pass

C. @pytest.autouse()
def setup():
pass

D. @pytest.usefixture(autouse=True)
def setup():
pass

Solution

1. Step 1: Recall correct syntax for autouse fixture

   The correct decorator is @pytest.fixture with the argument autouse=True.

2. Step 2: Check each option's syntax

   Only @pytest.fixture(autouse=True) def setup(): pass uses @pytest.fixture(autouse=True) correctly. Others use invalid decorators or wrong argument names.

3. Final Answer:

   @pytest.fixture(autouse=True) def setup(): pass -> Option B

4. Quick Check:

   Use @pytest.fixture(autouse=True) for autouse [OK]

Hint: Remember: autouse is a parameter in @pytest.fixture [OK]

Common Mistakes:

• Using @pytest.autouse decorator which does not exist
• Writing autouse as auto=True
• Using @pytest.usefixture instead of @pytest.fixture

3. Given the code below, what will be the output when running pytest?

import pytest

@pytest.fixture(autouse=True)
def setup():
    print('Setup runs')


def test_one():
    print('Test one running')


def test_two():
    print('Test two running')

medium

A. Test one running\nTest two running

B. Setup runs\nSetup runs\nTest one running\nTest two running

C. Setup runs\nTest one running\nSetup runs\nTest two running

D. Setup runs\nTest one running\nTest two running

Solution

1. Step 1: Understand autouse fixture behavior

   The autouse fixture runs automatically before each test function in the module.

2. Step 2: Trace the print statements during test runs

   For test_one: 'Setup runs' then 'Test one running'. For test_two: 'Setup runs' then 'Test two running'.

3. Final Answer:

   Setup runs\nTest one running\nSetup runs\nTest two running -> Option C

4. Quick Check:

   Autouse runs before each test = output B [OK]

Hint: Autouse fixture runs before every test automatically [OK]

Common Mistakes:

• Assuming fixture runs only once
• Ignoring print inside fixture
• Thinking tests run without setup prints

4. What is wrong with the following autouse fixture code?

import pytest

@pytest.fixture(autouse=True)
def setup():
    print('Setup')

@pytest.fixture
def test_data():
    return 42


def test_example(test_data):
    assert test_data == 42

medium

A. There is no error; the code works correctly

B. The test_data fixture cannot be used with autouse fixtures

C. The autouse fixture setup() does not yield or return, so cleanup is impossible

D. The autouse fixture setup() must accept a parameter

Solution

1. Step 1: Review fixture definitions and usage

   setup() is an autouse fixture that runs automatically and prints 'Setup'. test_data() is a normal fixture returning 42.

2. Step 2: Check if any syntax or usage errors exist

   Both fixtures are valid. Autouse fixtures do not need parameters or yield unless cleanup is needed. test_example uses test_data correctly.

3. Final Answer:

   There is no error; the code works correctly -> Option A

4. Quick Check:

   Autouse fixture without yield is valid [OK]

Hint: Autouse fixtures can be simple setup without yield [OK]

Common Mistakes:

• Expecting autouse fixtures must yield for cleanup
• Thinking autouse conflicts with other fixtures
• Assuming autouse fixtures need parameters

5. You want an autouse fixture to run once per test class, not before every test method. Which scope value should you use with @pytest.fixture(autouse=True)?

hard

A. "session"

B. "module"

C. "function"

D. "class"

Solution

1. Step 1: Understand pytest fixture scopes

   Scope "function" runs before each test function, "class" runs once per test class, "module" once per module, "session" once per test session.

2. Step 2: Match desired behavior to scope

   To run once per test class, use scope="class" with autouse=True.

3. Final Answer:

   "class" -> Option D

4. Quick Check:

   Scope "class" runs once per test class [OK]

Hint: Use scope='class' for autouse fixture once per test class [OK]

Common Mistakes:

• Using default scope 'function' which runs before every test
• Confusing 'module' with 'class' scope
• Using 'session' which runs too broadly