Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Improve StrictMock & mock_callable exception messages #234

Open
fornellas opened this issue Sep 1, 2020 · 0 comments
Open

Improve StrictMock & mock_callable exception messages #234

fornellas opened this issue Sep 1, 2020 · 0 comments
Assignees
@fornellas
Labels
Better Error Messages enhancement New feature or request Hacktoberfest

Comments

@fornellas
Copy link
Contributor

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.
@fornellas fornellas added the enhancement New feature or request label Sep 1, 2020
@fornellas fornellas self-assigned this Sep 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@fornellas fornellas

Labels
Better Error Messages enhancement New feature or request Hacktoberfest
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@deathowl @fornellas