Repository navigation
Document composing pytest fixtures with a shared RequestsMock - #845
Open
Pavel-Shcherbo wants to merge 1 commit into
Open
Pavel-Shcherbo wants to merge 1 commit into
Pavel-Shcherbo wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When API mocks are supplied by separate pytest fixtures, nesting independent
RequestsMockcontexts does not combine their routes. This documents a shared function-scoped context that API-specific fixtures populate, with a runnable two-API example.Refs #779.
The accompanying tests exercise each API fixture independently, both together in either fixture-argument order, shared instance identity, and fresh registries/call history for each test. The standard unused-response assertion remains enabled. No library behavior changes.
Validation on Python 3.14.6 / Requests 2.34.2:
The full tox/Python compatibility matrix was not run locally. These examples exercise existing behavior; they are not failing-before/passing-after library regressions.