chore: Use idiomatic Jest patterns to assert exceptions #1909
Conversation
This file contains 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
Avoid unnecessary assertions such as `expect(true).toBe(false)`. Instead, assert the exception using the `toThrow()` matcher. Where that is insufficient, use `expect.assertions()`. Unwrap exceptions in promises using `expect.rejects`. These patterns are documented at: - https://jestjs.io/docs/expect#tothrowerror - https://jestjs.io/docs/tutorial-async#rejects - https://jestjs.io/docs/expect#expectassertionsnumber
jdufresne
changed the title
KTibow
reviewed
Dec 27, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Avoid unnecessary assertions such as
expect(true).toBe(false). Instead, assert the exception using thetoThrow()matcher. Where that is insufficient, useexpect.assertions(). Unwrap exceptions in promises usingexpect.rejects.These patterns are documented at: