Changes expect().resolves.toThrow behaviour to more closely match jest #14936
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.
What does this PR do?
Fixes #14076
toThrow is for functions, like
expect(() => {throw ...}).toThrow()
, but jest also allows it to be used withresolves
/rejects
if the value is an error:expect(Promise.resolve(new Error("abc"))).resolves.toThrow("abc")
.Previously, bun's implementation allowed any result to count as throwing, for example
expect(Promise.resolve("abc")).resolves.toThrow("abc")
. This updates bun:test to match jest and only count an Error result throwing.How did you verify your code works?
bun-debug test test-file-name.test
)