When some static key doesn't match, Object matcher fails all keys that should match to regexp

[4ekki]

🐛 Bug Report

When some static key doesn't match, Object matcher fails all keys that should match to regexp

To Reproduce

Run the following test:

test("asdf", async () => {
  const actual = {
    a: "a_value",
    b: "b_value", 
    c: "c_value"
  }
  expect(actual).toMatchObject({
    a: expect.stringMatching("[a-z]_value"), 
    b: "b_value", 
  })

  expect(actual).toMatchObject({
    a: expect.stringMatching("[a-z]_value"), 
    b: "B_VALUE", 
  })
})

Actual behavior

Matcher reports keys 'a' and 'b' as mismatched:

Expected value to match object:
  {"a": StringMatching /[a-z]_value/, "b": "B_VALUE"}
Received:
  {"a": "a_value", "b": "b_value", "c": "c_value"}
Difference:
- Expected
+ Received

  Object {
-   "a": StringMatching /[a-z]_value/,
-   "b": "B_VALUE",
+   "a": "a_value",
+   "b": "b_value",
  }

Expected behavior

Only 'b' key is reported as failed:

   Object {
    -   "b": "B_VALUE",
    +   "b": "b_value",

[4ekki]

This one is quite annoying since it's hiding real problems in the output.

[garyking]

Any workaround for this for now? Just test individual object paths instead of the whole thing with toMatchObject, I guess?

[thymikee]

@pedrottimark is this on your roadmap to improve error messages of core matchers?

[4ekki]

Any update regarding this issue?

[dandv]

Have been seeing this issue for a few months; still there in v24.

[jeysal]

Unfortunately, this is all but trivial to fix, see #7027 (comment)
I believe this should be marked as duplicate of #6184?

[SimenB]

Yeah, duplicate of #6184

[github-actions]

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.