Skip to content

docs: clarify request fixture in indirect parametrization #14260

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mitre88 wants to merge 2 commits into
base: main
Choose a base branch
from
+6 −0
Open

docs: clarify request fixture in indirect parametrization #14260

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2c0d0e1
docs: clarify request fixture in indirect parametrization
mitre88 Mar 5, 2026
d6c4e10
changelog: add fragment for request fixture docs clarification
mitre88 Mar 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions changelog/13155.doc.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
Clarified in the parametrization examples that the built-in ``request`` fixture is used for indirect parametrization and that values are available through ``request.param``.
5 changes: 5 additions & 0 deletions doc/en/example/parametrize.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -356,6 +356,11 @@ Using the ``indirect=True`` parameter when parametrizing a test allows one to
parametrize a test with a fixture receiving the values before passing them to a
test:

The fixture receives the built-in ``request`` fixture object as its first
argument. For indirect parametrization, each value from
``@pytest.mark.parametrize`` is available as ``request.param`` inside that
fixture.

.. code-block:: python

import pytest
Expand Down