.toThrow() to match both error constructor and message?

[OpenGG]

I want to request a feature.

What is the current behavior?

Currently .toThrow() can match error constructor or message, but not both: demo

expect(()=>{
  throw new Error('1234');
}).toThrow(Error, 'hello'); // passes, but not what users may expect

Instead, I have to do it like this: demo

const matcher = expect(()=>{
  throw new Error('1234');
});
matcher.toThrow(Error);
matcher.toThrow('1234');

What is the expected behavior?

Is it possible .toThrow() can be refactored to match both error constructor and message at the same time, if message is provided?

expect(()=>{
  throw new Error('1234');
}).toThrow(Error);  // error constructor

expect(()=>{
  throw new Error('1234');
}).toThrow('1234'); // string to match message

expect(()=>{
  throw new Error('1234');
}).toThrow(/1234/); // regex to match message

expect(()=>{
  throw new Error('1234');
}).toThrow(Error, '1234');  // error constructor with string to match message

expect(()=>{
  throw new Error('1234');
}).toThrow(Error, /1234/);  // error constructor with regex to match message

[cpojer]

Please feel free to implement your own matcher with this feature using expect.extend.

[Nevon]

Is this still the official position? I find myself wanting to do this, but without #6243 it's not really possible to overload the behavior of toThrow, so it would have to be a completely separate matcher.

[SimenB]

Yeah, I think so. You can probably get it added to jest-extended, if you want.

@mattphillips

[mattphillips]

@Nevon I've just opened up this issue in jest-extended to add this matcher if you want to help out by sending a PR 👍

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