#steve-0_webhooks
errant elbowBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1379472151664394407
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- steve-0_webhooks, 6 days ago, 16 messages
still dagger
To be clear, four hours is still a long time for our automated tests
unkempt basin
Hello, I am looking in to this, though this is part of why we recommend mocking out the Stripe responses for automated tests rather than making API calls in our test environment. The stripe-mock server we made isn't advanced enough for this, but there are tools out there like VCR gem that make it easy to record and re-serve responses for automated tests
still dagger
we have other tests that do that
this is an e2e test that tests the full integration though
unkempt basin
Can you explain more of what you mean by that? We typically don't support automated testing that actually uses stripe.js or our APIs