When a subscription checkout changes, there are several things to check: did the app create a subscription-mode Checkout Session, did it use the expected recurring Price, did Stripe create the subscription, and did the app process the related events?
Those checks are related, but they are not the same test. Treating them as one all-or-nothing browser script can make failures hard to interpret—especially when the hosted payment page itself is difficult to automate.
I’m building SubTest , an open-source local CLI for repeatable Stripe subscription checks.
1. Check the Checkout Session contract
SubTest follows browser steps that you configure for your application, captures the test Checkout Session your app creates, then checks that Session through Stripe’s API.…