✅ Deploy Preview for jestjs ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	c751ae0
🔍 Latest deploy log	https://app.netlify.com/sites/jestjs/deploys/6794bcc34f8eef00083e3272
😎 Deploy Preview	https://deploy-preview-15463--jestjs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@SimenB I was wondering if the behavior in this issue is intentional? Imo, it doesn't make sense to treat them as the same. (i will open a PR, it if its a valid issue). Thanks!

@phryneas @SimenB Hey, can you take a look at this PR? It would be greatly appreciated!

@mohammednumaan I'm not a maintainer of jest, just a contributor - sorry ^^

This PR is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 30 days.

not stale

When trying to upgrade my team to v30 I found this bug was being used in asymetric matching to assert on the array length. I couldn't see an alternative approach now that this has been fixed.

For example, this used to pass, but now fails when trying to assert on the length of list

expect(testFunc).toHaveBeenLastCalledWith(
    expect.objectContaining({
        someArray: expect.arrayContaining([
            expect.objectContaining({
                list: expect.objectContaining({ length: 2 }),
            }),
        ]),
    }),
);

My workaround has been to switch to an array filled with an expect.anything()

expect(testFunc).toHaveBeenLastCalledWith(
    expect.objectContaining({
        someArray: expect.arrayContaining([
            expect.objectContaining({
                list: new Array(2).fill(expect.anything())
            }),
        ]),
    }),
);

My workaround has been to switch to an array filled with an expect.anything()

I think it is valid solution.

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.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.