Improve StrictMock & mock_callable exception messages
Ouverte
Better Error Messages
enhancement
Hacktoberfest
- Langage dominant
- Python
- Étoiles
- 149
- Forks
- 62
- Métriques de merge des PR
- Aucune PR mergée en 30 j
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.
Guide de contribution
Ouvrir le guide de contribution
Évaluation
Cette issue n'a pas encore été évaluée.