You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See that some tests fail which should pass while other tests pass which should fail.
Expected behavior
Using objectContaining to assert objects contain a property with a Map value when that Map has different entries than the expectation should fail.
// This should fail, but it passesexpect({aMap: newMap([[1,1]])}).toEqual(expect.objectContaining({aMap: newMap([[2,2]]),}));
Using not.objectContaining to assert objects do not contain a property with an identical Map value should pass when the entries are not identical.
// This should pass, but it failsexpect({aMap: newMap([[1,1]])}).toEqual(expect.not.objectContaining({aMap: newMap([[2,2]]),}));
Using expect().not.toEqual(expect.objectContaining()) to assert objects do not contain a property with an identical Map value should pass when the entries are not identical.
// This should pass, but it failsexpect({aMap: newMap([[1,1]])}).not.toEqual(expect.objectContaining({aMap: newMap([[2,2]]),}));
Actual behavior
Using objectContaining to assert objects contain a property with a Map value when that Map has different entries than the expectation passes.
Using not.objectContaining to assert objects do not contain a property with an identical Map value fails even when the entries are not identical.
Using expect().not.toEqual(expect.objectContaining()) to assert objects do not contain a property with an identical Map value fails even when the entries are not identical.
Additional context
It would seem that when matching against Map values, expect.objectContaining will always pass and expect.not.objectContaining will always fail. This may be related to these issues:
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 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.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.
Version
29.4.3
Steps to reproduce
yarn
yarn test
Expected behavior
objectContaining
to assert objects contain a property with a Map value when that Map has different entries than the expectation should fail.not.objectContaining
to assert objects do not contain a property with an identical Map value should pass when the entries are not identical.expect().not.toEqual(expect.objectContaining())
to assert objects do not contain a property with an identical Map value should pass when the entries are not identical.Actual behavior
Using
objectContaining
to assert objects contain a property with a Map value when that Map has different entries than the expectation passes.Using
not.objectContaining
to assert objects do not contain a property with an identical Map value fails even when the entries are not identical.Using
expect().not.toEqual(expect.objectContaining())
to assert objects do not contain a property with an identical Map value fails even when the entries are not identical.Additional context
It would seem that when matching against Map values,
expect.objectContaining
will always pass andexpect.not.objectContaining
will always fail. This may be related to these issues:Environment
The text was updated successfully, but these errors were encountered: