#kevin_docs

1 messages ยท Page 1 of 1 (latest)

stoic hollowBOT
#

๐Ÿ‘‹ 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/1424745741934395505

๐Ÿ“ 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.

sudden tartan
#

You can use these above test cards

slate violet
#

For example, when I submit, I do something like this

    const { error: submitError, selectedPaymentMethod: stripeSelectedPaymentMethod } = await elements.submit();

    if (submitError) {
      setErrorMessage(submitError.message);
      return;
    }

So what I need to do is to mock the response of elements.submit(); depending on my situation? Just want to be sure in case I'm missing documentation about how to do unit test with Stripe NPM library

sudden tartan
#

Yes, you're exactly right.

slate violet
#

Okay TY ๐Ÿ™