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.
Currently we raise things like
UnexpectedCallArgumentstelling about "behavior". This confuses a lot of users constantly.@karlodwyer suggested doing things like:
Le's apply this "make it clearer mindset" to all existing StrictMock & mock_callable exceptions.