-
Notifications
You must be signed in to change notification settings - Fork 212
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
chore(payments): clean Up Test Output #13182
Conversation
ebbf8e7
to
7d7ba6b
Compare
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.
Ah so nice! The test output looks so much better!
I just have 2 change requests. It'd be great if we could reuse the <Head>
component. Regarding the act
it'd be nice to not have to use it, but it shouldn't block the PR if it's not an easy fix.
I did notice that there are still some console.logs showing up in the server
tests. If it's a simple fix, could you fix these as well? (See screenshot below)
packages/fxa-payments-server/src/components/CouponForm/index.test.tsx
Outdated
Show resolved
Hide resolved
9cd6fce
to
2281f66
Compare
I was not able to block the output in your screenshot, at least my few hours of attempts were unfruitful. What makes those different from blocking similar output in this PR is that those logging statements use a different logger (mozlog) and the calls to the logger are not coming from the tests, they are coming from the server.js and route-logging.js files. For a few test files the server has to be instantiated with the call |
Because: * The payments test output is overly verbose for the logger tests and also contains some warnings that need to be addressed This commit: * overrides the console for logger tests, cleans up some react tests so that all interactions/side effects are accounted for, updates how the page title is displayed (its lifecycle events are deprecate and unavailable in react 17), and adds a check for if the cancelSubscriptionPanel component is mounted before a specific state update is applied (this is a memory leak apparently) Closes #13011
2281f66
to
752f09c
Compare
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.
LGTM. Thank you for the changes.
Because:
This commit:
Closes #13011
Checklist
Put an
x
in the boxes that apply