Fixture request object in PyTest - Build an Automation Script

Verify access to test function name using pytest fixture request object

Preconditions (2)

Step 1: Create a fixture that accepts the 'request' object as a parameter

Step 2: Inside the fixture, get the name of the test function using request.node.name

Step 3: Return the test function name from the fixture

Step 4: Create a test function that uses this fixture

Step 5: Assert inside the test that the fixture returns the correct test function name

✅ Expected Result: The test passes, confirming the fixture correctly accessed the test function name via the request object

Automation Requirements - pytest

Assertions Needed:

Assert that the fixture returns the exact name of the test function

Best Practices:

Use the pytest 'request' fixture parameter to access test context

Keep fixtures simple and focused

Use assert statements with clear messages

Name fixtures clearly

Automated Solution

PyTest

import pytest

@pytest.fixture
def test_name_fixture(request):
    # Access the current test function name
    return request.node.name


def test_example(test_name_fixture):
    # The fixture should return the name of this test function
    assert test_name_fixture == 'test_example', f"Expected 'test_example' but got {test_name_fixture}"

This code defines a fixture test_name_fixture that takes the special request object provided by pytest. The fixture uses request.node.name to get the name of the currently running test function.

The test function test_example uses this fixture and asserts that the returned name matches its own name. This confirms the fixture correctly accessed the test context.

Using the request object is a common way in pytest to get information about the test being run, which helps in writing dynamic or context-aware fixtures.

Common Mistakes - 3 Pitfalls

{'mistake': "Not including 'request' as a parameter in the fixture function", 'why_bad': "Without the 'request' parameter, the fixture cannot access the test context and will fail or not work as intended.", 'correct_approach': "Always include 'request' as a parameter in the fixture function to access the request object."}

{'mistake': 'Trying to access test function name outside the fixture or test function', 'why_bad': 'The test context is only available during test execution; accessing it elsewhere leads to errors or None values.', 'correct_approach': "Access test context only inside fixtures or test functions that receive the 'request' object."}

Hardcoding the expected test function name in the assertion without matching the actual test function

Bonus Challenge

Now add data-driven testing with 3 different test function names using the fixture to verify each name dynamically

Show Hint

Practice

1. What is the primary purpose of the request object in pytest fixtures?

easy

A. To provide information about the current test and allow dynamic fixture use

B. To execute test cases in parallel

C. To generate test reports automatically

D. To mock external APIs during tests

Solution

1. Step 1: Understand the role of the request object

   The request object in pytest is passed to fixtures to give them context about the current test being run.

2. Step 2: Identify its main uses

   It allows fixtures to access test metadata and dynamically use other fixtures or test info.

3. Final Answer:

   To provide information about the current test and allow dynamic fixture use -> Option A

4. Quick Check:

   request object = test info provider [OK]

Hint: Remember: request gives fixture info about the running test [OK]

Common Mistakes:

• Thinking request runs tests
• Confusing request with test report generation
• Assuming request mocks APIs

2. Which of the following is the correct way to access the current test function name inside a fixture using the request object?

easy

A. request.func_name

B. request.test.name

C. request.node.name

D. request.current_test

Solution

1. Step 1: Recall how pytest stores test info in request

   The request object has a node attribute representing the test item.

2. Step 2: Identify the attribute for test function name

   The test function name is stored in request.node.name.

3. Final Answer:

   request.node.name -> Option C

4. Quick Check:

   Test name = request.node.name [OK]

Hint: Use request.node.name to get test function name [OK]

Common Mistakes:

• Using request.test.name which does not exist
• Trying request.func_name instead of node.name
• Assuming request.current_test is valid

3. Given the following fixture code, what will be printed when the test test_example runs?

import pytest

@pytest.fixture
def show_test_name(request):
    print(f"Running test: {request.node.name}")


def test_example(show_test_name):
    assert True

medium

A. Running test: test_example

B. Running test: show_test_name

C. Running test: test_example(show_test_name)

D. No output printed

Solution

1. Step 1: Understand fixture usage

   The fixture show_test_name prints the current test function name using request.node.name.

2. Step 2: Identify the test function name

   The test function is test_example, so request.node.name will be "test_example".

3. Final Answer:

   Running test: test_example -> Option A

4. Quick Check:

   Fixture prints test function name [OK]

Hint: request.node.name prints the current test function name [OK]

Common Mistakes:

• Confusing fixture name with test name
• Expecting no output because of assert
• Thinking the full call signature prints

4. Identify the error in this fixture code that tries to access a marker from the request object:

@pytest.fixture
def check_marker(request):
    marker = request.marker.get('slow')
    if marker:
        print("Slow test")

medium

A. Markers cannot be accessed from request object

B. request.marker should be request.node.get_closest_marker()

C. request.marker is correct but missing parentheses

D. The fixture must return marker, not print

Solution

1. Step 1: Check how to access markers in pytest

   Markers are accessed via request.node.get_closest_marker('name'), not request.marker.

2. Step 2: Identify the correct method call

   The code should use request.node.get_closest_marker('slow') to get the marker.

3. Final Answer:

   request.marker should be request.node.get_closest_marker() -> Option B

4. Quick Check:

   Use request.node.get_closest_marker() for markers [OK]

Hint: Use request.node.get_closest_marker('name') to access markers [OK]

Common Mistakes:

• Using request.marker which does not exist
• Forgetting to call get_closest_marker() with parentheses
• Assuming markers can't be accessed in fixtures

5. How can you use the request object inside a fixture to dynamically use another fixture by name?

hard

A. Fixtures cannot call other fixtures dynamically

B. Use request.use_fixture('fixture_name') to call it

C. Import the fixture directly and call it inside the fixture

D. Call request.getfixturevalue('fixture_name') inside the fixture

Solution

1. Step 1: Understand dynamic fixture usage

   pytest allows fixtures to request other fixtures dynamically using the request object.

2. Step 2: Identify the correct method

   The method to get another fixture by name is request.getfixturevalue('fixture_name').

3. Final Answer:

   Call request.getfixturevalue('fixture_name') inside the fixture -> Option D

4. Quick Check:

   Dynamic fixture call = request.getfixturevalue() [OK]

Hint: Use request.getfixturevalue('name') to call fixtures dynamically [OK]

Common Mistakes:

• Using non-existent request.use_fixture() method
• Trying to import fixtures manually inside fixtures
• Believing fixtures cannot call others dynamically