Custom Error Exceptions properties are not evaluated for strict equality

🐛 Bug Report

Custom properties on objects constructed from a Class that extends Error are not evaluated when matched with either .toThrow or .toThrowError.

To Reproduce

1. Create a custom class that extends the Error object.

Class CustomError extends Error {
  constructor(message, code) {
    super(message);
    this.code = code;
  }
}

1. Create a custom error object using class constructor.

const customError = new CustomError('something wrong happened', 'ERR_CUSTOM_CODE');

1. In the code that needs to be tested, throw that custom error.

function fnThatThrowNoMatterWhat() {
   throw customError;
}

1. In the test, try to pass a new instance of that custom error object (created in the test file) and pass it to .toThrowError.

const expectedError = new CustomError('something wrong happened', 'WRONG_ERR_CUSTOM_CODE');
 expect(() => main()).toThrowError(expectedError); // pass when it should fail

Expected behavior

All properties added to the object are checked strictly and not just message.

Acceptance criteria:

• https://repl.it/repls/CurvyFrightenedNumber must fail
• https://repl.it/repls/ThirstySwelteringAggregators must pass

Link to repl or repo (highly encouraged)

repl.it example

Run npx envinfo --preset jest

Paste the results here:

  System:
    OS: Linux 4.15 Ubuntu 18.04.1 LTS (Bionic Beaver)
    CPU: x64 Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz
  Binaries:
    Node: 8.10.0 - ~/.nvm/versions/node/v8.10.0/bin/node
    Yarn: 1.9.2 - /usr/bin/yarn
    npm: 6.3.0 - ~/.nvm/versions/node/v8.10.0/bin/npm

[runarberg]

Note:

• AVA’s .throws returns the error object so you can do arbitrary tests on it.
• Chai’s .throw expectation can be chained with other assertions like .with.property('code', 42).

Here is a stack overflow answer for overcoming this limitation of jest.

[github-actions[bot]]

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.