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.
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
mbeliaev/loose matcher #498
mbeliaev/loose matcher #498
Conversation
Codecov Report
@@ Coverage Diff @@
## master #498 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 6 6
Lines 2162 2184 +22
=========================================
+ Hits 2162 2184 +22
Continue to review full report at Codecov.
|
tests fail, #495 should fix it |
5cc62fe
to
c6d0114
Compare
responses/matchers.py
Outdated
|
||
if not valid: | ||
reason = "Parameters do not match. {} doesn't match {}".format( | ||
_create_key_val_str(request_params_dict), | ||
_create_key_val_str(params_dict), | ||
) | ||
if not strict_match: | ||
reason += "\nNote that you use not strict parameters check." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
reason += "\nNote that you use not strict parameters check." | |
reason += "\nYou can use `strict_match=False` to use enable matches." |
What do you think of this? It makes the error more instructive on what a next step could be.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
agree with the idea, but I think the message should be "You can use 'strict_match=True' to do a strict parameters check."
since now this reason is triggered when strict_match=False
Closes #496