Improve StrictMock & mock_callable exception messages
Open
Better Error Messages
enhancement
Hacktoberfest
- Dominant language
- Python
- Stars
- 149
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
Currently we raise things like `UnexpectedCallArguments` telling about "behavior". This confuses a lot of users constantly.
@karlodwyer suggested doing things like:
- UnexpectedCallArguments > UnmatchedCallReceived
- explain there's no configured mocks to answer this call
- explain which calls the mock is configured to accept.
Le's apply this "make it clearer mindset" to all existing StrictMock & mock_callable exceptions.
Contributor guide
Assessment
This issue has not been assessed yet.