#wzm-stripejs-ci-testing
smoky hinge
stable wolf
Hello! Is there a reason you're doing this? We continually tweak our fraud/abuse systems so I wouldn't be surprised if that would result in your requests timing out
weak hawk
Yes, we're simulating payment page visits, so make sure no code changes on our side broke payments. We stub out requests to stripe, but stripe.js is supposed to always be fetched directly from you, not saved off and used locally.
stable wolf
Unfortunately CI testing isn't really something that we support very well - I assume you're running these tests after every code change? Instead of doing it after every change it may be worth doing it batches?