-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
expect.any() does not match in toMatchObject if other keys mismatch #11765
Comments
Looks like #6184, but the bot locked that issue (thanks?) so I can't continue the discussion there. |
Hey @dandv, Which version of Jest are you running? ( Replit seems to be terribly outdated and running Node 12 and Jest 23. 😬 Everything looks a-ok here running your test on Jest 27. |
This issue is stale because it has been open for 1 year with no activity. Remove stale label or comment or this will be closed in 30 days. |
This issue was closed because it has been stalled for 30 days with no activity. Please open a new issue if the issue is still relevant, linking to this one. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
🐛 Bug Report
When comparing two objects with
toMatchObject
, if a literal key differs, others keys are reported to not matchexpect.any(...)
even if they do.To Reproduce
Link to repl
https://replit.com/@dandv1/jest-bug-9298#bug9298.test.js
envinfo
Other info
Possibly related: #9298.
I'm also pretty sure someone else has filed this bug but I can't find it, and GitHub no longer shows similar issues when creating a new one.
The text was updated successfully, but these errors were encountered: