-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
fix(expect): support arbitrary value equality for toThrow and make Error detection robust
#9570
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
sheremet-va
merged 7 commits into
vitest-dev:main
from
hi-ogawa:fix/cross-realm-error-tothrow
Feb 3, 2026
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
27e8a64
fix(expect): support cross-realm errors in toThrow matcher
hi-ogawa 8142016
test: tweak
hi-ogawa da3617c
docs: update toThrow/toThrowError documentation and types
hi-ogawa e6488c6
chore: disable no-throw-literal for docs
hi-ogawa aacc027
fix: loosen class equality
hi-ogawa 6973695
test: update
hi-ogawa 4c4fdd1
Merge branch 'main' into fix/cross-realm-error-tothrow
hi-ogawa File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -8,7 +8,6 @@ | |
|
|
||
| import type { Test } from '@vitest/runner' | ||
| import type { MockInstance } from '@vitest/spy' | ||
| import type { Constructable } from '@vitest/utils' | ||
| import type { Formatter } from 'tinyrainbow' | ||
| import type { AsymmetricMatcher } from './jest-asymmetric-matchers' | ||
| import type { diff, getMatcherUtils, stringify } from './jest-matcher-utils' | ||
|
|
@@ -535,8 +534,9 @@ export interface JestAssertion<T = any> extends jest.Matchers<void, T>, CustomMa | |
| * @example | ||
| * expect(() => functionWithError()).toThrow('Error message'); | ||
| * expect(() => parseJSON('invalid')).toThrow(SyntaxError); | ||
| * expect(() => { throw 42 }).toThrow(42); | ||
| */ | ||
| toThrow: (expected?: string | Constructable | RegExp | Error) => void | ||
| toThrow: (expected?: any) => void | ||
|
|
||
| /** | ||
| * Used to test that a function throws when it is called. | ||
|
|
@@ -546,8 +546,9 @@ export interface JestAssertion<T = any> extends jest.Matchers<void, T>, CustomMa | |
| * @example | ||
| * expect(() => functionWithError()).toThrowError('Error message'); | ||
| * expect(() => parseJSON('invalid')).toThrowError(SyntaxError); | ||
| * expect(() => { throw 42 }).toThrowError(42); | ||
| */ | ||
| toThrowError: (expected?: string | Constructable | RegExp | Error) => void | ||
| toThrowError: (expected?: any) => void | ||
|
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The documentation already had |
||
|
|
||
| /** | ||
| * Use to test that the mock function successfully returned (i.e., did not throw an error) at least one time | ||
|
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This prototype check is loosened to match our default
toEqualbehavior. This also becomes ourtoThrowErrorequality, so that got loosened as seen intest/core/test/jest-expect.test.ts. I think it's expected that users would need to dotoStrictEqualto opt-in stricter check (though that's not directly possible viatoThrowError). I consider this change as a valid fix.