`expect(...).rejects.toThrow()` should not be passing for rejected promises.

[dmaretskyi]

Describe the bug

If I correctly understand the behaviour of toThrow from the docs, it should fail when the value passed to expect is not a function; yet, this test passes:

import { test } from 'vitest';

test('expect rejects toThrow', async ({ expect }) => {
  const promise = Promise.reject(new Error('Test'));
  await expect(promise).rejects.toThrow();
});

Reproduction

https://stackblitz.com/edit/vite-ssr-map-sources-csbrts?file=repro.test.js

System Info

System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.20.3 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    vite: ^5.4.7 => 5.4.7 
    vitest: ^2.1.1 => 2.1.1

Used Package Manager

pnpm

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[sheremet-va]

If I correctly understand the behaviour of toThrow from the docs, it should fail when the value passed to expect is not a function; yet, this test passes:

The "tip" only applies to sync toThrow. .rejects correctly unwraps the promise.

PR is welcome to add the note to the documentation