-
Notifications
You must be signed in to change notification settings - Fork 0
π§ͺ Add unit tests for ErrorMessages component #478
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
Closed
Closed
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,40 @@ | ||
| // @vitest-environment jsdom | ||
| import { render, screen } from "@testing-library/react"; | ||
| import { describe, it, expect } from "vitest"; | ||
| import ErrorMessages from "./ErrorMessages"; | ||
| import "@testing-library/jest-dom"; | ||
|
|
||
| describe("ErrorMessages", () => { | ||
| it("returns null when errors array is empty", () => { | ||
| const { container } = render(<ErrorMessages errors={[]} />); | ||
| expect(container.firstChild).toBeNull(); | ||
| }); | ||
|
|
||
| it("returns null when errors is undefined", () => { | ||
| // Typecast to any to test the falsy condition handled in the component | ||
| // eslint-disable-next-line @typescript-eslint/no-explicit-any | ||
| const { container } = render(<ErrorMessages errors={undefined as any} />); | ||
| expect(container.firstChild).toBeNull(); | ||
| }); | ||
|
|
||
| it("renders a single error message", () => { | ||
| const errors = [{ section: "API", message: "Failed to fetch data" }]; | ||
| render(<ErrorMessages errors={errors} />); | ||
|
|
||
| expect(screen.getByText(/API:/)).toBeInTheDocument(); | ||
| expect(screen.getByText(/Failed to fetch data/)).toBeInTheDocument(); | ||
| }); | ||
|
|
||
| it("renders multiple error messages", () => { | ||
| const errors = [ | ||
| { section: "API", message: "Failed to fetch data" }, | ||
| { section: "Database", message: "Connection timeout" } | ||
| ]; | ||
| render(<ErrorMessages errors={errors} />); | ||
|
|
||
| expect(screen.getByText(/API:/)).toBeInTheDocument(); | ||
| expect(screen.getByText(/Failed to fetch data/)).toBeInTheDocument(); | ||
| expect(screen.getByText(/Database:/)).toBeInTheDocument(); | ||
| expect(screen.getByText(/Connection timeout/)).toBeInTheDocument(); | ||
| }); | ||
| }); | ||
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.
The multiple-error test checks each section and each message as separate text nodes. If the component renders the API section with the Database message and the Database section with the API message, all four assertions still pass, so this test misses the visible section-to-message mismatch.
Prompt To Fix With AI