[Docs]: toThrow fails if error object contains a `cause` property

[kirkwaiblinger]

Page(s)

https://jestjs.io/docs/expect#tothrowerror

Description

When attempting to use the toThrow() method to validate an exact error message, I expected the following code to pass, according to the docs.

expect((async () => { throw new Error('message', { cause: new Error('cause') }); })()).rejects.toThrow(new Error('message'))

However, it fails with error

expect(received).rejects.toThrow(expected)

- Expected message            - 1
+ Received message and cause  + 8

That's reasonable behavior, but it should be documented as such.

[kirkwaiblinger]

This appears to occur in the synchronous case as well:

    expect(() => {
      throw new Error('message', { cause: new Error('cause') });
    }).toThrow(new Error('message'));

output:

    expect(received).toThrow(expected)

    Expected message:           "message"
    Received message and cause: "{ message: message, cause: { message: cause }}"

but doesn't occur if cause is just a string....

In summary:

  it("should pass, but doesn't, async case", async () => {
    await expect(
      (async () => {
        throw new Error('message', { cause: new Error('cause') });
      })(),
    ).rejects.toThrow(new Error('message'));
  });

  it("should pass, but doesn't, sync case", () => {
    expect(() => {
      throw new Error('message', { cause: new Error('cause') });
    }).toThrow(new Error('message'));
  });

  it('should pass, does pass', () => {
    expect(() => {
      throw new Error('message', { cause: 'cause' });
    }).toThrow(new Error('message'));
  });

TBH it seems like this may be a bug, not just undocumented behavior

[github-actions]

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

[github-actions]

This issue was closed because it has been stalled for 30 days with no activity. Please open a new issue if the issue is still relevant, linking to this one.

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