Fixture request object in PyTest - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the request fixture object in pytest?

The request fixture object in pytest gives access to information about the executing test function, like its name, module, and allows accessing other fixtures dynamically.

beginner

How do you use the request object to get the name of the current test function?

You can get the current test function name using request.node.name inside a fixture or test.

intermediate

Explain how to access another fixture dynamically using the request object.

Use request.getfixturevalue('fixture_name') to get the value of another fixture inside a fixture or test.

intermediate

What is a practical use case for the request fixture object?

It helps customize fixture behavior based on the test function name or parameters, or to access other fixtures dynamically for flexible test setups.

beginner

True or False: The request object can only be used inside test functions, not fixtures.

False. The request object is commonly used inside fixtures to get test context or access other fixtures.

What does request.node.name return in pytest?

A The current test function's name

B The name of the fixture

C The module name

D The test result status

request.node.name returns the name of the currently running test function.

How can you access another fixture inside a fixture using the request object?

A request.call('fixture_name')

B request.usefixture('fixture_name')

C request.access('fixture_name')

D request.getfixturevalue('fixture_name')

Use request.getfixturevalue('fixture_name') to get another fixture's value dynamically.

Which of these is NOT accessible via the request object?

A Test execution time

B Current test function name

C Test module name

D Fixture scope

The request object does not provide test execution time information.

True or False: The request fixture is automatically available in all test functions without declaring it.

A Only in fixtures

B True

C False

D Only in classes

You must explicitly declare request as a parameter to use it in tests or fixtures.

What is a common reason to use the request object in a fixture?

A To generate test reports

B To get test context like test name or parameters

C To skip tests automatically

D To run tests in parallel

The request object helps get test context such as the test name or parameters inside fixtures.

Describe how the pytest request fixture object can be used inside a fixture to customize behavior based on the current test function.

Think about how knowing the test name helps change what the fixture does.

Explain how to dynamically access another fixture inside a pytest fixture using the request object and why this might be useful.

Consider cases where you want to reuse fixtures without hardcoding dependencies.

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