#zak_stripejs-testing
last parrotBOT
👋 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/1230283367887671408
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
hoary estuary
I've also tried with 10001 with the same result.
Also, strangely, I don't see these errors in the Stripe logs.
fathom drumBOT
sick schooner
👋 Hey I'm really sorry totally missed your question earlier, let me read
@hoary estuary which "element" are you using? CardElement or PaymentElement?
If you use PaymentElement, the postal code is based on the country we think you're in based on your IP address. So if you run this in CI and it seems that the IP is not in the US we'd expect a different postal code format.
Also: we actively discourage that kind of testing entirely and would recommend never to do that.
zak_stripejs-testing
hoary estuary
hey
adding a pause before submitting helped apparently
can you explain why it's actively discouraged?
I'm using Payment Element to answer the earlier question
sick schooner
We control the code and regularly change the element and HTML underlying code. So tests like this are brittle and tend to not scale.
hoary estuary
I see... my director of engineering really likes E2E testing though so I think we are OK keeping an eye on the tests and maintaining them if that's not an issue with you guys. It's not going to be more than 10 tests overall.
sick schooner
yep I'm more flagging because it can feel like a "cat and mouse" game to try to patch your tests each time we change something