#vincent_code
severe questBOT
đ 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/1292902005789954092
đ 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.
- vincent_best-practices, 5 days ago, 15 messages
peak dawn
hey Hanzo. nice to see you again.
dull dome
Hello
We generally recommend just mocking the logic where you touch Stripe SDK code.. For example: https://docs.stripe.com/automated-testing#client-side-testing
Instead of calling Stripe.js functions, you'd just call your own mock function that returns a mocked response..
peak dawn
ill drill into this.
to be more specific though, i am just trying to get the PaymentElement and AddressElement to simply render in the test context. Is it even possible to your knowledge to see that in a react-testing-library/jest/enzyme test?
dull dome
I don't think its possible no..