toHaveProperty returning unexpected result

[evictor]

Do you want to request a feature or report a bug?

bug

What is the current behavior?

Oddly, toHaveProperty is incorrectly marking a failure. As you can see in the error details below, it should be passing:

19:15:04     Expected the object:
19:15:04       {"_id": "5a7bc0b6d44d9300287bc66b", "examAnswerSpecId": "ageGroup14AndUnder", "examQuestionSpecId": "ageGroup"}
19:15:04     To have a nested property:
19:15:04       "examQuestionSpecId"
19:15:04     With a value of:
19:15:04       "ageGroup"
19:15:04 
19:15:04       59 |     expect(exam.answers).toHaveLength(1)
19:15:04       60 |     const retrievedAnswer = exam.answers[0]
19:15:04     > 61 |     expect(retrievedAnswer).toHaveProperty('examQuestionSpecId', q.id)
19:15:04       62 |     expect(retrievedAnswer).toHaveProperty('examAnswerSpecId', a.id)
19:15:04       63 |   })
19:15:04       64 | })

The test passes when I convert the expect from using toHaveProperty to an 'ordinary' expectation:

expect(retrievedAnswer.examQuestionSpecId).toEqual(q.id)

Please provide your exact Jest configuration and mention your Jest, node,
yarn/npm version and operating system.

Jest version: v22.1.4
Node version: v9.4.0
npm version: 5.6.0
OS: Linux e902ac7b5568 4.4.0-104-generic #127-Ubuntu SMP Mon Dec 11 12:16:42 UTC 2017 x86_64 GNU/Linux

Jest configuration is vanilla—verbose mode on, and a setup file specified that does app-specific stuff.

[SimenB]

Can you create a reproduction case we can pull down?

[evictor]

I created this repo but it's not reproducing... So going to close this for now.

[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.