Parametrize with indirect fixtures in PyTest - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does 'indirect=True' do in pytest's parametrize decorator?

It tells pytest to pass the parameter value to a fixture instead of directly to the test function. The fixture then processes the parameter before the test runs.

intermediate

How do indirect fixtures help when you want to prepare test data differently for each parameter?

Indirect fixtures let you customize setup logic for each parameter value, like creating different test objects or configurations, by receiving the parameter and returning the prepared data.

beginner

Example: What will happen if you use @pytest.mark.parametrize('input', [1, 2], indirect=True) with a fixture named 'input'?

The fixture 'input' will be called twice, once with 1 and once with 2 as parameter values. The test function will receive the fixture's return value each time.

intermediate

Why might you prefer indirect parametrization over direct parametrization?

Because indirect parametrization allows complex setup or transformation of parameters before the test runs, making tests cleaner and more flexible.

beginner

What is a common mistake when using indirect fixtures with parametrize?

A common mistake is forgetting to name the fixture the same as the parameter or not setting indirect=True, which causes pytest to pass the parameter directly instead of through the fixture.

What does setting indirect=True in @pytest.mark.parametrize do?

A Skips the test for that parameter

B Passes the parameter to a fixture for processing

C Runs the test multiple times without parameters

D Directly passes the parameter to the test function

Setting indirect=True tells pytest to send the parameter to a fixture instead of directly to the test function.

If you parametrize 'data' with indirect=True, what must exist?

A A fixture named 'data'

B A test function named 'data'

C A global variable named 'data'

D A class named 'data'

The parameter name must match a fixture name to use indirect parametrization.

Why use indirect parametrization in pytest?

A To customize setup logic for each parameter

B To skip tests automatically

C To run tests in parallel

D To reduce test execution time

Indirect parametrization allows you to customize how each parameter is prepared before the test runs.

What happens if you forget indirect=True but want to use a fixture?

A The fixture is ignored

B The test fails to run

C The test runs only once

D The parameter is passed directly to the test function

Without indirect=True, pytest passes parameters directly to the test function, not through the fixture.

Which of these is a valid use of indirect parametrization?

A @pytest.mark.parametrize('config', [1, 2, 3])

B @pytest.mark.parametrize('config', ['dev', 'prod'])

C @pytest.mark.parametrize('config', ['dev', 'prod'], indirect=True)

D @pytest.mark.parametrize('config', None)

Option C uses indirect=True to pass 'dev' and 'prod' to a fixture named 'config' for setup.

Explain how indirect parametrization works in pytest and why it is useful.

Think about how fixtures can prepare data differently for each parameter.

Describe a scenario where indirect parametrization would be better than direct parametrization.

Consider when test inputs require special preparation before testing.

Practice

1. What does using indirect=True in @pytest.mark.parametrize do in pytest?

easy

A. It skips the test when the parameter is None.

B. It disables the fixture for that test.

C. It runs the test only once regardless of parameters.

D. It passes the parameter value to a fixture instead of directly to the test function.

Solution

1. Step 1: Understand parametrize behavior

   Normally, parameters are passed directly to the test function as arguments.

2. Step 2: Effect of indirect=True

   When indirect=True is set, pytest sends the parameter value to the fixture instead, allowing setup logic to use it.

3. Final Answer:

   It passes the parameter value to a fixture instead of directly to the test function. -> Option D

4. Quick Check:

   indirect=True means parameter goes to fixture [OK]

Hint: Indirect means parameter goes to fixture, not test directly [OK]

Common Mistakes:

• Thinking parameters always go directly to test functions
• Confusing indirect=True with skipping tests
• Assuming indirect disables fixtures

2. Which of the following is the correct syntax to parametrize a test with an indirect fixture named data for values 1 and 2, when there are other direct parameters?

easy

A. @pytest.mark.parametrize('data', [1, 2], indirect=True)

B. @pytest.mark.parametrize('data', [1, 2], indirect=['data'])

C. @pytest.mark.parametrize('data', [1, 2], indirect=False)

D. @pytest.mark.parametrize('data', [1, 2], indirect=None)

Solution

1. Step 1: Recall indirect parameter usage

   When only some parameters are indirect, you pass a list of their names to indirect.

2. Step 2: Apply to single parameter

   For one parameter data, indirect=['data'] is correct syntax.

3. Final Answer:

   @pytest.mark.parametrize('data', [1, 2], indirect=['data']) -> Option B

4. Quick Check:

   indirect=['param_name'] for indirect fixture [OK]

Hint: Use indirect=['param_name'] to mark specific params indirect [OK]

Common Mistakes:

• Using indirect=True for single param when multiple params exist
• Passing indirect=False or None which disables indirect
• Not using a list for indirect parameter names

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

import pytest

@pytest.fixture
def data(request):
    return request.param * 2

@pytest.mark.parametrize('data', [3, 5], indirect=True)
def test_double(data):
    print(data)

medium

A. 6 and 10

B. 3 and 5

C. None and None

D. Error: request.param not found

Solution

1. Step 1: Understand fixture with request.param

   The fixture data returns request.param * 2, so it doubles the parameter.

2. Step 2: Parametrize with indirect=True

   Parameters 3 and 5 are passed to the fixture, so the test receives 6 and 10.

3. Final Answer:

   6 and 10 -> Option A

4. Quick Check:

   Fixture doubles param: 3*2=6, 5*2=10 [OK]

Hint: Indirect param goes to fixture; fixture doubles it [OK]

Common Mistakes:

• Thinking parameters go directly to test, so expecting 3 and 5
• Assuming request.param is unavailable causing error
• Confusing fixture return with test parameter

4. What is wrong with this pytest code snippet?

@pytest.fixture
def setup_data(request):
    return request.param + 1

@pytest.mark.parametrize('setup_data', [10, 20])
def test_increment(setup_data):
    assert setup_data in [11, 21]

medium

A. The fixture should not return a value.

B. Fixture name and parameter name must be different.

C. Missing indirect=True in parametrize to pass parameters to fixture.

D. The assert statement is incorrect.

Solution

1. Step 1: Check parametrize usage with fixture

   Parameters must be passed indirectly to fixtures using indirect=True.

2. Step 2: Identify missing indirect=True

   The code lacks indirect=True, so parameters go directly to test, not fixture.

3. Final Answer:

   Missing indirect=True in parametrize to pass parameters to fixture. -> Option C

4. Quick Check:

   indirect=True needed to use request.param [OK]

Hint: Add indirect=True to parametrize when using request.param [OK]

Common Mistakes:

• Forgetting indirect=True causes request.param error
• Thinking fixture and param names must differ
• Assuming fixture cannot return values

5. You want to test a fixture config that reads a file path from parameters and loads data. You have two file paths: "file1.json" and "file2.json". How do you correctly parametrize the test to pass these paths to the fixture using indirect parametrization, when there are other direct parameters?

hard

A. @pytest.mark.parametrize('config', ["file1.json", "file2.json"], indirect=['config'])

B. @pytest.mark.parametrize('config', ["file1.json", "file2.json"])

C. @pytest.mark.parametrize('config', ["file1.json", "file2.json"], indirect=True)

D. @pytest.mark.parametrize('config', ["file1.json", "file2.json"], indirect=False)

Solution

1. Step 1: Identify indirect parameter usage for single fixture

   When passing parameters to a fixture, use indirect=['fixture_name'] to mark that parameter indirect.

2. Step 2: Apply to config fixture

   Since only config is indirect, use indirect=['config'] with the list of file paths.

3. Final Answer:

   @pytest.mark.parametrize('config', ["file1.json", "file2.json"], indirect=['config']) -> Option A

4. Quick Check:

   Use indirect=['config'] to pass params to fixture [OK]

Hint: Use indirect=['fixture_name'] to pass params to fixture [OK]

Common Mistakes:

• Using indirect=True instead of list for single param
• Not using indirect causing fixture to miss parameters
• Setting indirect=False disables indirect passing