Fixture request object in PyTest - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to access the test function name using the request fixture.

PyTest

def test_example(request):
    test_name = request.[1]
    assert test_name == 'test_example'

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

Afixturename

Bnode.name

Cparam

Dconfig

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'request.param' which is for parameterized fixtures.

Trying to access 'request.config' which is for pytest config.

Using 'request.fixturename' which is not a valid attribute.

The request fixture's node.name attribute gives the current test function's name.

2fill in blank

medium

Complete the code to get the current test module's filename using the request fixture.

PyTest

def test_module_name(request):
    module_file = request.node.[1]
    assert module_file.endswith('.py')

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

Amodule.__file__

Bmodule.file

Cmodule.filename

Dmodule.path

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'module.file' which does not exist.

Using 'module.filename' which is not a valid attribute.

Using 'module.path' which is not correct.

The request.node.module.__file__ attribute gives the filename of the test module.

3fill in blank

hard

Fix the error in the code to correctly access the test class name using the request fixture.

PyTest

def test_class_name(request):
    cls_name = request.node.[1]
    assert cls_name == 'TestExample'

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

Aparent.__name__

Bclass.__name__

Ccls.__name__

Dmodule.__name__

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'class' keyword which is reserved in Python.

Using 'parent' which is not an attribute of request.node.

Using 'module.__name__' which gives module name, not class name.

The test class name is accessed via 'request.node.cls.__name__'.

4fill in blank

hard

Fill both blanks to create a fixture that uses the request object to print the current test function name and module.

PyTest

@pytest.fixture
def print_test_info(request):
    print('Running:', request.node.[1])
    print('Module:', request.node.[2].__file__)

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

Aname

Bmodule

Ccls

Dparent

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'cls' instead of 'name' for function name.

Using 'parent' which is not valid.

Mixing up module and class attributes.

request.node.name gives the test function name; request.node.module gives the module object.

5fill in blank

hard

Fill all three blanks to write a fixture that skips a test if the test function name contains 'skip'.

PyTest

import pytest

@pytest.fixture(autouse=True)
def skip_if_name_contains_skip(request):
    if 'skip' in request.node.[1]:
        pytest.[2](reason='Skipped because test name contains skip')

    yield

    # Post-test code can go here

# Example test

def test_skip_example():
    assert True

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

Aname

Bskip

Cskipif

Dskip(reason='')

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'skipif' as a function instead of a decorator.

Trying to call 'skip' with parentheses in options.

Using wrong attribute instead of 'name'.

Use 'request.node.name' to get the test name, and 'pytest.skip' to skip the test during runtime.

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