Test subscription lifecycles with test clocks

In this episode, you'll learn how to move objects through time in test mode.

Test clocks make it easier to test your Billing integration and make sure it behaves as designed. When you use test clocks you simulate the forward movement of time in test mode, which causes resources, like Subscriptions, to change state and trigger webhook events. This means that, e.g., you don’t have to wait a year to see how your integration handles a payment failure for a quarterly or annual renewal.

### Presenter
CJ Avilla - Developer Advocate at Stripe - https://twitter.com/cjav_dev

### Resources
API Reference: https://stripe.com/docs/api/test_clocks
Documentation: https://stripe.com/docs/billing/testing/test-clocks

### Table of contents
00:00 Introduction
00:58 Create a new test clock
01:46 Attach the test clock to a customer
03:05 Create a subscription
03:58 Advance a subscription in time
06:02 Test a future subscription cancellation
06:24 Delete a test clock
06:41 Recap


### Support
If you have a question, please feel free to reach out to our support team on Discord at https://stripe.com/go/developer-chat

### Updates
Sign up to stay updated with developer news: https://go.stripe.global/dev-digest

### Feedback
If you have any feedback about this or other episodes, let us know: https://forms.gle/VjNqzRhotM2snYo88
#Stripe #Payments