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