Skip to content

docs: clarify request fixture in indirect parametrization#14260

Open
mitre88 wants to merge 2 commits intopytest-dev:mainfrom
mitre88:patch-5
Open

docs: clarify request fixture in indirect parametrization#14260
mitre88 wants to merge 2 commits intopytest-dev:mainfrom
mitre88:patch-5

Conversation

@mitre88
Copy link
Contributor

@mitre88 mitre88 commented Mar 5, 2026

Summary

Clarify the request fixture usage in the "Indirect parametrization" example.

This change explicitly states that:

  • request is the built-in fixture object passed to fixtures.
  • indirect values from @pytest.mark.parametrize(..., indirect=True) are available as request.param.

Closes #13155

mitre88 added 2 commits March 5, 2026 14:02
Explain that `request` is the built-in fixture object and that `request.param` carries each indirect parameter value.
Add changelog/13155.doc.rst to satisfy changelog checks for PR pytest-dev#14260.
@psf-chronographer psf-chronographer bot added the bot:chronographer:provided (automation) changelog entry is part of PR label Mar 5, 2026
@webknjaz
Copy link
Member

webknjaz commented Mar 6, 2026

Is there a place in the docs that could be linked as request.params?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bot:chronographer:provided (automation) changelog entry is part of PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

DOCS, BUG: Using and clarifying the request fixture.

2 participants