Skip to content
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

Add "where to patch" link to the docs #387

Merged
merged 3 commits into from
Oct 13, 2023
Merged

Add "where to patch" link to the docs #387

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ea1d0a6
Add "where to patch" link to the docs
nicoddemus Oct 6, 2023
53cc0a5
Update usage.rst
nicoddemus Oct 6, 2023
cec59a0
Update usage.rst
nicoddemus Oct 7, 2023
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
9 changes: 9 additions & 0 deletions docs/usage.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -157,3 +157,12 @@ function decorators for mocking unnecessary, so it will emit a warning when used

If you really intend to mock a context manager, ``mocker.patch.context_manager`` exists
which won't issue the above warning.

Where to patch
--------------

A common issue where mocking appears not to be working is patching in the wrong place.

See this `section in the unittest docs <https://docs.python.org/3/library/unittest.mock.html#where-to-patch>`__ which provides a comprehensive explanation.

Also see this excellent blog post: `Why your mock doesn't work <https://nedbatchelder.com/blog/201908/why_your_mock_doesnt_work.html>`__.