inxilpro - checkout tests | Stripe Developers | Page 1

cobalt wedge Sep 1, 2022, 3:32 PM

#

Hi there one moment

#

Yeah the recommended way to test things is to use mocks

#

We have this library that may help your usecase: https://github.com/stripe/stripe-mock

GitHub

GitHub - stripe/stripe-mock: stripe-mock is a mock HTTP server that...

stripe-mock is a mock HTTP server that responds like the real Stripe API. It can be used instead of Stripe's testmode to make test suites integrating with Stripe faster and less brittle. - ...

golden mountain Sep 1, 2022, 3:34 PM

#

But stripe-mock doesn't have a way to mock a Checkout session, does it?

#

The problem is that finalizing a Checkout session triggers about 20 events, and right now, the only way to know what those events are is by recording the results of a manual test.

#

And I would imagine that how checkout works will probably change over time

#

Which means that if I hard-code a bunch of mocks now, that test won't represent reality if checkout ever changes

#

That one POST to /v1/payment_pages/{id} triggers all of these events:

customer.created
coupon.created
coupon.updated
charge.succeeded
payment_method.attached
checkout.session.completed
customer.updated
customer.discount.created
customer.discount.deleted
invoice.created
invoice.finalized
customer.subscription.created
invoice.updated
customer.subscription.updated
invoice.paid
invoice.payment_succeeded
payment_intent.created
payment_intent.succeeded
invoice.upcoming
invoice.created

cobalt wedge Sep 1, 2022, 3:42 PM

#

Yeah Stripe mock is mostly just used for generating proper api responses for calls

#

Unfortunately there's not a good way to automate that checkout flow in tests other than the approach you outlined

#

Is there a reason you need all these events?

golden mountain Sep 1, 2022, 3:43 PM

#

I would like my test to be as close to production as possible. That way, if we add listeners for one of those events in the future, our tests would pick up any new bugs we introduce.

cobalt wedge Sep 1, 2022, 3:45 PM

#

Gotcha. Checkout is constantly evolving so yeah I do recommend manual testing with a test card when making a change like that.

golden mountain Sep 1, 2022, 3:45 PM

#

Right now I really only care about customer.subscription.updated and invoice.payment_succeeded, but if I eventually add code that triggers on invoice.paid, my existing test won't catch any issues with that.

#

Hm, OK.

#

Well, I'd love to put in a feature request for /v1/test_helpers/checkout/sessions/:id/complete or something similar that I could pass a payment method to to simulate completing a session.

cobalt wedge Sep 1, 2022, 3:53 PM

#

Sure thing. I'll pass this along to the Checkout team. There won't be any guarantees though on implementation/time frame due to prioritization

golden mountain Sep 1, 2022, 3:53 PM

#

Thanks.

#

It looks like stripe-cli kind of does this with the trigger checkout.session.completed function

sturdy cedar Sep 1, 2022, 3:55 PM

#

👋 stepping in for codename_duchess as they need to step away

#

Is there anything else I can help with here?

#inxilpro - checkout tests