Why advanced fixtures handle complex scenarios in PyTest - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a simple pytest fixture.

PyTest

import pytest

@pytest.fixture
def [1]():
    return 42

Drag options to blanks, or click blank then click option'

Afixture_func

Bsimple_fixture

Csetup

Dtest_func

Attempts:

3 left

💡 Hint

Common Mistakes

Using names that start with 'test_' which pytest treats as test functions.

Using invalid Python names or reserved keywords.

The fixture name must be a valid Python function name. Here, simple_fixture is a clear and valid name.

2fill in blank

medium

Complete the code to use a fixture in a test function.

PyTest

def test_answer([1]):
    assert [1] == 42

Drag options to blanks, or click blank then click option'

Asimple_fixture

Bsetup

Cfixture_func

Danswer

Attempts:

3 left

💡 Hint

Common Mistakes

Using a parameter name different from the fixture name.

Forgetting to include the fixture as a parameter.

The test function must accept the fixture name as a parameter to use it. Here, simple_fixture matches the fixture defined earlier.

3fill in blank

hard

Fix the error in the fixture that uses yield for setup and teardown.

PyTest

import pytest

@pytest.fixture
def resource():
    print('Setup')
    [1] 10
    print('Teardown')

Drag options to blanks, or click blank then click option'

Areturn

Bbreak

Cyield

Dpass

Attempts:

3 left

💡 Hint

Common Mistakes

Using return instead of yield in fixtures needing teardown.

Placing teardown code before yield.

Using yield in a fixture allows setup before the yield and teardown after. return would end the function immediately without teardown.

4fill in blank

hard

Fill both blanks to create a fixture that depends on another fixture and modifies its value.

PyTest

@pytest.fixture
def modified_resource([1]):
    value = [2] + 5
    return value

Drag options to blanks, or click blank then click option'

Aresource

Csimple_fixture

Dsetup

Attempts:

3 left

💡 Hint

Common Mistakes

Using a fixture name that does not exist.

Not passing the dependent fixture as a parameter.

The fixture modified_resource depends on the resource fixture. It receives resource as a parameter and adds 5 to it.

5fill in blank

hard

Fill all three blanks to create a parametrized fixture that runs tests with multiple inputs.

PyTest

@pytest.fixture(params=[1, 2, 3])
def param_fixture([1]):
    return [2]

def test_param([3]):
    assert [3] > 0

Drag options to blanks, or click blank then click option'

Arequest

Brequest.param

Cparam_fixture

Dparams

Attempts:

3 left

💡 Hint

Common Mistakes

Using params as a parameter name in the fixture function.

Not using request.param to get the current parameter.

Not passing the fixture to the test function.

The fixture uses request to access the current parameter with request.param. The test function receives the fixture param_fixture as a parameter.

Practice

1. What is the main reason to use advanced fixtures in pytest?

easy

A. To avoid writing any assertions

B. To write tests without any setup

C. To make tests run slower

D. To manage complex setup and cleanup for tests

Solution

1. Step 1: Understand the role of fixtures

   Fixtures in pytest help prepare the environment before tests run and clean up after tests finish.

2. Step 2: Identify why advanced fixtures are used

   Advanced fixtures handle more complex setup and teardown tasks, making tests clearer and more reliable.

3. Final Answer:

   To manage complex setup and cleanup for tests -> Option D

4. Quick Check:

   Advanced fixtures = manage complex setup [OK]

Hint: Fixtures handle setup and cleanup tasks [OK]

Common Mistakes:

• Thinking fixtures remove the need for assertions
• Believing fixtures slow down tests intentionally
• Assuming fixtures eliminate all test code

2. Which of the following is the correct syntax to define a fixture in pytest?

easy

A. def fixture(): pass

B. @pytest.fixture
def my_fixture(): pass

C. @fixture
def my_fixture(): pass

D. def my_fixture() @pytest.fixture: pass

Solution

1. Step 1: Recall pytest fixture syntax

   Fixtures are defined by decorating a function with @pytest.fixture.

2. Step 2: Check each option

   @pytest.fixture def my_fixture(): pass correctly uses @pytest.fixture decorator before the function definition.

3. Final Answer:

   @pytest.fixture\ndef my_fixture(): pass -> Option B

4. Quick Check:

   @pytest.fixture decorator = correct syntax [OK]

Hint: Use @pytest.fixture decorator before function [OK]

Common Mistakes:

• Forgetting the @pytest.fixture decorator
• Using @fixture without pytest prefix
• Placing decorator after function definition

3. Given the code below, what will be printed when running the test?

import pytest

@pytest.fixture
def resource():
    print('Setup resource')
    yield 'data'
    print('Cleanup resource')

def test_example(resource):
    print(f'Using {resource}')

medium

A. Setup resource\nUsing data\nCleanup resource

B. Using data\nSetup resource\nCleanup resource

C. Setup resource\nCleanup resource\nUsing data

D. Using data only

Solution

1. Step 1: Understand fixture execution order

   The fixture runs setup code before the test (prints 'Setup resource'), then yields the value.

2. Step 2: Trace test and fixture cleanup

   The test prints 'Using data'. After test finishes, fixture runs cleanup code (prints 'Cleanup resource').

3. Final Answer:

   Setup resource\nUsing data\nCleanup resource -> Option A

4. Quick Check:

   Setup -> Test -> Cleanup order = C [OK]

Hint: Fixture setup runs before test, cleanup after [OK]

Common Mistakes:

• Assuming cleanup runs before test
• Thinking yield returns after test ends
• Ignoring print order in fixture

4. Identify the error in this fixture code that causes the test to fail:

import pytest

@pytest.fixture
def setup_db():
    connection = open_db()
    return connection
    close_db(connection)

def test_query(setup_db):
    assert setup_db.is_connected()

medium

A. assert statement is incorrect

B. Fixture should not return any value

C. close_db(connection) is never called due to return before it

D. open_db() is not defined

Solution

1. Step 1: Analyze fixture return and cleanup

   The fixture returns connection before calling close_db(connection), so cleanup never runs.

2. Step 2: Understand proper cleanup in fixtures

   Cleanup code after return is unreachable; use yield to run cleanup after test.

3. Final Answer:

   close_db(connection) is never called due to return before it -> Option C

4. Quick Check:

   Return before cleanup skips cleanup [OK]

Hint: Use yield for cleanup after test, not return [OK]

Common Mistakes:

• Placing cleanup code after return statement
• Not using yield for teardown
• Assuming return runs cleanup code

5. You want to share a database connection across multiple tests but ensure it is created only once and closed after all tests finish. Which advanced fixture feature should you use?

hard

A. Use fixture with scope='module' and yield for setup and teardown

B. Use a simple function without fixture decorator

C. Create connection inside each test separately

D. Use fixture with autouse=False and no yield

Solution

1. Step 1: Understand fixture scopes

   Setting scope='module' makes fixture run once per module, sharing resource across tests.

2. Step 2: Use yield to manage setup and teardown

   Yield allows setup before tests and cleanup after all tests using the fixture.

3. Final Answer:

   Use fixture with scope='module' and yield for setup and teardown -> Option A

4. Quick Check:

   Scope='module' + yield = shared setup/cleanup [OK]

Hint: Use scope='module' and yield for shared resource cleanup [OK]

Common Mistakes:

• Creating resource in each test causing overhead
• Not using yield so cleanup never runs
• Using autouse without scope causing multiple setups