#JohnTheFrog
main zealot
*nor payload of incoming webhooks
slow narwhal
hello! are you referring to the https://site-admin.stripe.com/docs/api/events/object#event_object-created
and that isn't the test clock timestamp?
slow narwhal
i'm not sure i understand your question correctly, can you try rephrasing what's the problem you're facing?
main zealot
If the test clock starts advancing, there goes an test_helpers.test_clock.advancing
event through the webhook. This event does not contain a timestamp what is the target time of that advancing process
This is a problem for me since I need to mock that time during other webhooks
Example webhook order looks like that
- test_helpers.test_clock.advancing - no data about target timestamp
- invoice.upcoming - no data about target timestamp
3.invoice.created - no data about target timestamp - test_helpers.test_clock.ready - data about target timestamp exists, but I had no clue about its value during previous webhooks which generated wrong data in my custom flow
slow narwhal
can you share an example event id for the test_helpers.test_clock.advancing for us to take a look at?
main zealot
My final idea is to integrate test clocks with our backend system on test-environments so QA could test invoicing using stripes test clock
evt_1MwDXWGoLmBCnzj7SXorwoJt
jovial lakeBOT
main zealot
test_helpers.test_clock.advancing - evt_1MwDXWGoLmBCnzj7SXorwoJt
test_helpers.test_clock.ready - evt_1MwDXeGoLmBCnzj7J0pUWgMr
It would be great to have the target timestamp in advancing event payload since there are libraries like PHP's Carbon that can mock their current time using oneline solution. I guess many other libraries can do it too
acoustic jolt
Is that not the frozen_time field?
main zealot
no, the frozen_time value if different for advancing & ready event
I believed the advancing would have the same frozen_time as ready
so during advance event I have no idea what time I am trying to simulate 🤔
example event id for upcoming invoice during that advancing process: evt_1MwDXaGoLmBCnzj7z8EXuXmp
acoustic jolt
no, the frozen_time value if different for advancing & ready event
How is it? You specify frozen_time param when you advance the Test Clock
Sorry, I'm a tad confused
main zealot
- advancing 1686789244
- ready 1689381240
The advancing webhook event does not contain the target timestamp which is 1689381240
acoustic jolt
Yes, because in the .advanced event the frozen_time reflects the time of the Test Clock now, before it advances
I guess you want like a target_time field or similar, which just isn't available
main zealot
Yup
I just wanted to know if there is a way I can fetch that target_time, but if this isn't possible then I guess it is what it is and I will need to make a different workaround like write own panel for test clocks and call it from our system directly
main zealot
Thank you