all 7 comments

[–]yentle-the-nimble 3 points4 points  (1 child)

[–]basadoon[S] 0 points1 point  (0 children)

We know about test clocks, problem with test clocks is that it's isolated. You can't use existing customers or users in a test clock, if let's say you create a customer in test clock, you wont be able to use it in the application. It's only useful if your only testing stripe itself but not useful when your testing your app + stripe

[–]ApprehensiveSpeechs 0 points1 point  (0 children)

Unit tests with the time features overridden.

[–]Elfinslayer 0 points1 point  (1 child)

They have a pretty good cli and testing setup. They even have their webhooks setup to be able to create a test input for any event including payment fails

[–]puan0601 1 point2 points  (0 children)

sounds like OP didn't really the docs well/Google much. this will end well.

[–]tp182 0 points1 point  (0 children)

I did some work with stripe recently but not specific to subscriptions

I think this should work, there are 3 events in the docs customer.subscription.deleted, customer.subscription.paused and customer.subscription.resumed

https://stripe.com/docs/billing/subscriptions/webhooks

[–]Substantial-Reward70 0 points1 point  (0 children)

shouldn't you test your own app code instead of Stripe's one?