JohnTheFrog

[desert dagger]

Hello 👋
This error most likely means something in your code is trying to modify the clock before the clock is ready.

[gleaming knoll]

My test case looks like that:

0. create test clock
1. create payment method (4242424242424242 card)
2. Create customer with given payment method and clock
3. Move the clock back 1 year
4. Subscribe to annual price
5. Move the clock 6 month forward
6. Make the subscription monthly

Ah now I see. I can get the test clock status by quering it

So I can make a query to stripe api, ie. every 10 seconds for that test clock and check if the status is ready

[desert dagger]

You can, yes. If you have a webhook endpoint then I think we can also send a webhook event for this

This event specifically
https://stripe.com/docs/api/events/types#event_types-test_helpers.test_clock.ready

[gleaming knoll]

Hmmmm I don't think I can incorporate webhook into a unit test

But pooling is also fine, 10 sec is a long period I guess

(PHP / Laravel)

[desert dagger]

Gotcha. In certain cases, depending on the time you're advancing your clock to may take a bit longer to be ready.

[gleaming knoll]

I guess so. Thanks 🙂

[desert dagger]

NP! 🙂 Happy to help

[gleaming knoll]

Hmmm the clock is ready but the error still occurs

welp, I guess I will have to find other way around

[desert dagger]

Hmm, yeah not sure whats going on here.
We typically just recommend stubbing out the mock responses for unit testing

We also have this, feel free to take a look to see if that's something useful for ya
https://github.com/stripe/stripe-mock

[gleaming knoll]

I can't mock a behaviour I am unsure of 😄

The mock server looks neat, for sure it will be useful for rewriting some of the old tests

[desert dagger]

👍