Improve integration tests for deferred intent UPE #6882
Labels
component: stripe link
The issues/PRs related to the StripeLink project
component: tests
Issues related to tests
component: upe
needs tests
The issue/PR needs tests before it can move forward.
priority: low
The issue/PR is low priority—not many people are affected or there’s a workaround, etc.
type: technical debt
This issue/PR represents/solves the technical debt of the project.
Description
Currently, in our deferred intent UPE integration work, we have relied greatly on extending existing functionality. Our checkout code inherits the original UPE payment gateway class and relies on the legacy gateway's
process_payment
function to complete a checkout. Similarly our unit test coverage mostly consists of extending existing UPE unit tests. Consequently our unit test coverage is somewhat lacking in that we neglect to comprehensively the new deferred intent flows of logic from the UPE gateway to the legacy gateway, testing all components in concord concurrently.It would be nice if we could create some new unit tests that effectively test the deferred intent UPE checkout by ensuring that relevant functions are only fired when necessary, metadata is always added when relevant, and that redundant UPE function calls are no longer made.
Acceptance criteria
Here are a few things of the top of my head that would be nice to have specific integration test coverage for.
payment_method_types
,mandate_data
).Designs
N/A
Testing instructions
Exactly.
Dev notes
Additional context
#6391
The text was updated successfully, but these errors were encountered: