db1900_payment-element-testing | Stripe Developers | Page 1

inland egretBOT Apr 15, 2024, 4:13 PM

#

👋 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/1229464560843620382

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

agile ruinBOT Apr 15, 2024, 4:13 PM

#

ripe jewel Apr 15, 2024, 4:14 PM

#

Hi 👋

We don't generally recommend performing automated front-end testing using the Payment Element.

What workflows are you attempting to test here?

loud aspen Apr 15, 2024, 4:17 PM

#

we are attempting to test that the customer was able to setup a payment method

ripe jewel Apr 15, 2024, 4:20 PM

#

In that case i would manually go through the process in Test mode and collect the responses from the confirmSetup method in Stripe JS. Then, in your automated testing, you can use those stored responses in place of filling out the Payment Element.

loud aspen Apr 15, 2024, 4:23 PM

#

hmmm

#

essentially set the customer up before running the test? then we could mock out the response from the Stripe API call with the already created data?

ripe jewel Apr 15, 2024, 4:28 PM

#

Yes.

#

Furthermore, I'm not familiar with Cypress but I know our Elements <iframe> does not permit programmatic entry of card information so you won't be able to automate front-end testing of the element.

#db1900_payment-element-testing