-
Notifications
You must be signed in to change notification settings - Fork 0
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
My Account 2.0 #407
My Account 2.0 #407
Conversation
SCC-4253: Edit email in My Account 2.0
SCC-4236: Username for My Account 2.0
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
A couple small things that are not super crucial, so if you can include those that would be great. But the API client needs to be updated before this can go out.
) | ||
}) | ||
|
||
test("successfully sets patron data if every field is valid", async () => { |
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.
is this the correct title for this test?
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.
What might make more sense as the title for this test?
expect(screen.getByRole("button", { name: /edit/i })).toBeInTheDocument() | ||
}) | ||
|
||
it("renders correctly with when user has no username", () => { |
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.
can you add a few more tests here? there are a bunch of different combinations of isEditing/hasUsername/etc that are represented by these ternaries here.
This doesn't have to block QA deployment, but these expectations for these different cases should be tested. It will help with making updates from the QA process.
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.
I agree there should be more tests but they can also be written while the team starts the QA cycle.
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.
There are updates needed but approving to start the QA process.
expect(screen.getByRole("button", { name: /edit/i })).toBeInTheDocument() | ||
}) | ||
|
||
it("renders correctly with when user has no username", () => { |
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.
I agree there should be more tests but they can also be written while the team starts the QA cycle.
Ticket:
This PR does the following:
How has this been tested?
Accessibility concerns or updates
Checklist: