-
Notifications
You must be signed in to change notification settings - Fork 663
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
Refactor payment sheet event tests #10314
base: master
Are you sure you want to change the base?
Conversation
Diffuse output:
APK
|
a2aaf96
to
4a9c06c
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.
The link inline change LGTM. I'm not convinced that the PaymentSheetEventTest change is a net-positive, left a comment about that.
Also a tip for the future: I think this could have been two PRs (one for the link inline changes, one for the changes to PaymentSheetEventTest). Just makes it easier to review and also for you to get your changes merged
"is_decoupled" to false, | ||
"link_enabled" to false, | ||
"google_pay_enabled" to false, | ||
defaultPaymentSuccessEventParams.plus( |
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'm not sure there's much of an advantage to making this change -- it doesn't improve the error message if tests fail at all and it makes our tests less explicit (ie it's harder to tell what exactly we are asserting on). It does reduce duplication, but at the cost of making the tests less explicit and I'm not sure the trade off is worth it.
Summary
parameterizing some payment sheet event tests
factoring out defaultPaymentSuccessEventParams
made PaymentMethodFixtures.LINK_INLINE_PAYMENT_SELECTION
Motivation
Make testing easier.
Reduce technical debt.
Testing
Screenshots
N.A.
Changelog
N.A.