#julliian-test-subscription-events
hot pawn
austere flare
I've removed this btw ```js
if (subscription.status === 'canceled') {
inner flume
Hi 👋 you can update a Subscription in test mode to cause the event to trigger. Or you can use test clocks to progress a test Subscription through its lifecycle so the customer.subscription.updated events that are triggered each billing period are generated and sent:
https://stripe.com/docs/billing/testing/test-clocks
austere flare
Alright. I'll try that out.
Is it okey to use checkout.session.completed, or should I use the customer.subscription.created? If that's the right name
inner flume
Either works, which you should use depends on what information you need to access (checkout.session.completed events will contain the Checkout Session object, customer.subscription.created will contain the Subscription object), and what Events other parts of your integration generate that you need to avoid having trigger the downstream processes you're building.