-
Notifications
You must be signed in to change notification settings - Fork 42
Open
Description
I'm trying to test if my URLSearchParams
are correct with the to.deep.equal
option but it returns true
(is equal) when it shouldn't.
See the running code at https://stackblitz.com/edit/node-qx7qra?file=index.test.js
Let's assume that we're testing this function:
function getIncorrectParams() {
return new URLSearchParams({
from: '2020',
to: '2021',
ids: ['abc-1'],
});
}
If I write:
test('via string', () => {
expect(getIncorrectParams().toString()).not.to.equal(
new URLSearchParams({
from: '2020',
to: '2021',
ids: ['abc-1', 'abc-2'],
}).toString()
);
});
It correctly notices that the strings are not the same, good. But as soon as I remove the toString
and test with:
test('via deep equal', () => {
expect(getIncorrectParams()).not.to.deep.equal(
new URLSearchParams({
from: '2020',
to: '2021',
ids: ['abc-1', 'abc-2'],
})
);
});
It claims that the assertion failed because the two objects are "equal". Note if you actually go ahead and run the example, the debug output clearly shows that there are differences!
And the deep.equal
property works if I use "normal" object. See this example where I convert the URLSearchParams
to a "plain object" first:
test('deep equal plain objects', () => {
expect(Object.fromEntries(getIncorrectParams().entries())).not.to.deep.equal({
from: '2020',
to: '2021',
ids: ['abc-1', 'abc-2'],
});
});
Metadata
Metadata
Assignees
Labels
No labels