-
-
Notifications
You must be signed in to change notification settings - Fork 6.6k
expect: Improve report when matcher fails, part 18 #8356
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
Conversation
SimenB
left a comment
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.
Codecov Report
@@ Coverage Diff @@
## master #8356 +/- ##
==========================================
+ Coverage 62.23% 62.23% +<.01%
==========================================
Files 266 266
Lines 10716 10715 -1
Branches 2608 2607 -1
==========================================
Hits 6669 6669
Misses 3460 3460
+ Partials 587 586 -1
Continue to review full report at Codecov.
|
scotthovestadt
left a comment
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.
Looks great to me!
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |





Summary
For
toMatchObjectmatcher:rejectsorresolvesin matcher hintWhen negative assertion fails:
notbetween expected label and valueWhen positive assertion fails:
Differencelabel) or stringify values, not bothResidue: there is room for improvement through possible future data-driven diff
Faithful reviewers: thank you for heroic effort to go through
matchers.tstogether!toThrow(Class)intoThrowMatchers.jsspyMatchers.tsTest plan
toMatchObjectpass: failpass: truethrowsSee also pictures in following comment.