This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author taleinat
Recipients Adnan Umer, cheryl.sabella, cjw296, mariocj89, michael.foord, suhearsawho, taleinat, terry.reedy, xtreak
Date 2019-02-13.09:03:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1550048580.96.0.35616336327.issue35500@roundup.psfhosted.org>
In-reply-to
Content
Susan, I agree that similarly improving the failure message for assert_called_with would be good.

I find the final "Not called" line unclear, though. Perhaps something like the following:

AssertionError: expected call not found.
Expected: mock(1, 2, 3, 4)
Actual: Not called
History
Date User Action Args
2019-02-13 09:03:00taleinatsetrecipients: + taleinat, terry.reedy, cjw296, michael.foord, cheryl.sabella, mariocj89, xtreak, Adnan Umer, suhearsawho
2019-02-13 09:03:00taleinatsetmessageid: <1550048580.96.0.35616336327.issue35500@roundup.psfhosted.org>
2019-02-13 09:03:00taleinatlinkissue35500 messages
2019-02-13 09:03:00taleinatcreate