Skip to content
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

fix: cleaning up sso self service wording and behaviors #1093

Merged
merged 1 commit into from
Nov 21, 2023

Conversation

alex-sheehan-edx
Copy link
Contributor

For all changes

  • Ensure adequate tests are in place (or reviewed existing tests cover changes)

Only if submitting a visual change

  • Ensure to attach screenshots
  • Ensure to have UX team confirm screenshots

Copy link

codecov bot commented Nov 20, 2023

Codecov Report

Attention: 3 lines in your changes are missing coverage. Please review.

Comparison is base (c0e0bc1) 84.69% compared to head (15b95a0) 84.71%.

Files Patch % Lines
...nents/settings/SettingsSSOTab/NewSSOConfigCard.jsx 80.00% 1 Missing ⚠️
...nents/settings/SettingsSSOTab/NewSSOConfigForm.jsx 87.50% 1 Missing ⚠️
src/components/settings/SettingsSSOTab/index.jsx 88.88% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1093      +/-   ##
==========================================
+ Coverage   84.69%   84.71%   +0.01%     
==========================================
  Files         476      476              
  Lines        9958     9968      +10     
  Branches     2083     2089       +6     
==========================================
+ Hits         8434     8444      +10     
  Misses       1483     1483              
  Partials       41       41              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Comment on lines +112 to +114
act(() => {
userEvent.click(screen.getByTestId(`existing-sso-config-card-dropdown-${inactiveConfig[0].id}`));
});
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is act() needed here? It was my understanding that @testing-library/react userEvent operations are already wrapped in act().

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was just following and fixing the warnings printed out by the tests, I believe it has to do with updates triggered by the click and not just the click itself? However I'm not entirely sure

@alex-sheehan-edx alex-sheehan-edx merged commit d798b43 into master Nov 21, 2023
6 checks passed
@alex-sheehan-edx alex-sheehan-edx deleted the asheehan-edx/ENT-7985 branch November 21, 2023 15:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants