#slynonsensicalaardvark
calm wigeon
Hi 👋 just to make sure, is this automated testing that's going to run every time a build occurs? We typically discourage hitting our API in flows like that, as it is a good way to accidentally hit our rate limits:
https://stripe.com/docs/rate-limits
candid grotto
For our payment flows we could have it restricted to a manual trigger to reduce total number of calls (e.g. not every single build), but ideally we'd still be able to run it without manual setup
calm wigeon
Gotcha, so what is the redirect_uri you're referring to, where are you currently having to set that?
candid grotto
Looks like it's the list of "Redirects" (urls) in the Integration screen.
Disclosure: I'm new to this codebase but trying to help these folks out
"Specify all possible URIs that a user could be redirected to after completing the OAuth onboarding flow for Standard or Express"
calm wigeon
Ahh, alright, the redirects for OAuth flows for Connect. Just a quick aside, we no longer recommend OAuth for onboarding Connected Accounts. We now typically (there are some exceptions) recommend that you create new Connected Accounts instead.
That being said, I'm not aware of a way to automate the addition of those redirect locations. I'm pretty sure that must be done via the Stripe dashboard.
faint raftBOT
candid grotto
Ah fair enough. Does Stripe have a standard / official container for simulating stripe in testing situations?
calm wigeon
Our stripe-mock library is going to be the closest thing we have for that, it emulates the behavior of interacting with our API:
https://github.com/stripe/stripe-mock
candid grotto
Is stripe-mock the recommended way to incorporate end-to-end integration testing that requires stripe?