-
Notifications
You must be signed in to change notification settings - Fork 21
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
UIE-204 Narrow Ajax Usage pt12 #5173
Conversation
partial<UserContract>({ | ||
getSamUserCombinedState: jest.fn().mockResolvedValue(mockSamUserCombinedState), | ||
profile: { | ||
get: jest.fn(async () => partial<TerraUserProfile>({})), |
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 jest.fn inline form gives great type safety, whereas jest.fn().mockResolvedValue(...) has no type safety because of a cast to "any" out of jest.fn().
- shifting ajax usage to directly use ajax sub-areas for the user profile and registration areas. - improving mock types where possible.
- minor typo fix
- improved type safety in mocks for test in TermsOfServicePage.test.ts
db356c9
to
4c1db8b
Compare
Quality Gate passedIssues Measures |
Jira Ticket: https://broadworkbench.atlassian.net/browse/[Ticket #]
Summary of changes:
What
Why
Testing strategy