Inconsistency in `rejects.toThrow()`

🐛 Bug Report

The doc says the argument of toThrow() can be a class for the error, it works when a promise throws an Error instance, but fails when the promise throws a custom object.

To Reproduce

describe('When a promise throws an expression, rejects.toThrow should match the expression by its type', () => {
    it('when the expression is an error', async () => {
        const p = new Promise(() => {
            throw new Error('some-info');
        });
        await expect(p).rejects.toThrow(Error); // passed
    });
    it('when the expression is a custom object', async () => {
        class Exception {
            constructor(public readonly message: string) {
            }
        }

        const p = new Promise(() => {
            throw new Exception('some-info');
        });
        await expect(p).rejects.toThrow(Exception); // failed
    });
});

The first test passes, while the second test fails with the following message:

Expected the function to throw an error of type:
  "Exception"
But it didn't throw anything.

Expected behavior

Both the above two tests pass.

[MarcusPope]

This is also a problem when throwing objects in async/await that are not Error instances and expecting the toThrow() default with no arguments:

test("Bug in jest", async () => {
    expect(() => {
      throw "this is fine";
    }).toThrow();

    await expect(
      (async () => {
        throw new Error("this is fine too");
      })()
    ).rejects.toThrow();

    await expect(
      (async () => {
        throw "this is not fine";
      })()
    ).rejects.toThrow(); // FAILS TEST
  });

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