Skip to content

unittest.mock test and coverage fixup #130787

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.

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

Merged
merged 2 commits into from
Mar 3, 2025
Merged

Conversation

cjw296
Copy link
Contributor

@cjw296 cjw296 commented Mar 3, 2025

"no coverage" markers for two functions that will never be called along with a test fixup that was missing the path it intended to cover.

These were highlighted by coverage checking in the rolling backport.

cjw296 added 2 commits March 3, 2025 11:11
.stop() and __exit__ have subtly different code paths, so to really test __exit__ idempotency, we need to call it specifically twice.
@cjw296 cjw296 enabled auto-merge (squash) March 3, 2025 11:24
cjw296 added a commit to cjw296/mock that referenced this pull request Mar 3, 2025
@cjw296 cjw296 merged commit 04091c0 into python:main Mar 3, 2025
44 checks passed
seehwan pushed a commit to seehwan/cpython that referenced this pull request Apr 16, 2025
* Mark functions that will never be called with # pragma: no cover

* Fix testpatch.PatchTest.test_exit_idempotent

.stop() and __exit__ have subtly different code paths, so to really test __exit__ idempotency, we need to call it specifically twice.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant