Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(255606)

#21262: assert_not_called method for mocks

Can't Edit
Can't Publish+Mail
Start Review
Created:
5 years, 4 months ago by michael
Modified:
5 years, 4 months ago
Reviewers:
berker.peksag
CC:
Michael Foord, devnull_psf.upfronthosting.co.za, kushaldas
Visibility:
Public.

Patch Set 1 #

Total comments: 2
Unified diffs Side-by-side diffs Delta from patch set Stats Patch
Doc/library/unittest.mock.rst View 1 chunk +12 lines, -0 lines 1 comment Download
Lib/unittest/mock.py View 1 chunk +8 lines, -0 lines 1 comment Download
Lib/unittest/test/testmock/testmock.py View 1 chunk +9 lines, -0 lines 0 comments Download
Misc/NEWS View 1 chunk +3 lines, -0 lines 0 comments Download

Messages

Total messages: 2
berkerpeksag
http://bugs.python.org/review/21262/diff/11642/Doc/library/unittest.mock.rst File Doc/library/unittest.mock.rst (right): http://bugs.python.org/review/21262/diff/11642/Doc/library/unittest.mock.rst#newcode335 Doc/library/unittest.mock.rst:335: Needs a versionadded directive.
5 years, 4 months ago #1
Michael Foord
5 years, 4 months ago #2
http://bugs.python.org/review/21262/diff/11642/Lib/unittest/mock.py
File Lib/unittest/mock.py (right):

http://bugs.python.org/review/21262/diff/11642/Lib/unittest/mock.py#newcode765
Lib/unittest/mock.py:765: if not self.call_count == 0:
Use != instead of not ==
Sign in to reply to this message.

RSS Feeds Recent Issues | This issue
This is Rietveld 894c83f36cb7+