#oranges13_code
1 messages ยท Page 1 of 1 (latest)
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.
- oranges13_code, 3 days ago, 12 messages
๐ Welcome to your new thread!
โฒ๏ธ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1250153430404694076
๐ Have more to share? Add details, code, screenshots, videos, etc. below.
Hello! You can't force Google Pay to be shown, it will only show when using a browser that supports our specific Google Pay implementation and when a valid card is detected in the Google Pay wallet.
Do you see Google Pay in the Payment Element here? https://4242.io/test/payment-element/
I see it in one of my browsers (logged in with my personal google account) but not in my testing account because it's not logged into google.
Really? That's really going to put a wrench in our automated testing if it only appears sometimes.
You shouldn't be doing automated tests on our UI elements. You should mock the responses you get from them in your tests instead.
Our UI elements have a lot of security measures in place to prevent automating them (to prevent fraud and abuse) so it's difficult to get automated tests working right. Even if you do get them working, ongoing changes to our security measures are likely to break your tests in the future.
Our command line tests do mock responses but we have actual click-through testing via a browser to confirm site functionality
against a test stripe account though.
You shouldn't use test mode in automated tests either. ๐ Test mode is for developing and testing your integration as you're working on it, not to confirm behavior every time you build. Again, you should mock responses for automated testing.
That's not for build time, thats for QA-engineer-testing. They use tools like Jenkins / Selenium when testing features manually.
Our build tests definitely use mocking.
Ah, okay. Still, you're likely going to run into issues, either now or in the future, if you try to automate UI tests on our components.
But yeah, if we can't verify that google pay or apple pay are available that puts a wrinkle in what our stakeholders are probably hoping to achieive.. Local development with wallets is proving tricky anyway because we can't verify the localhost / test domains
Fun ๐ซ
OK well thank you, that testing tool above is helpful.
Yeah, sorry. It's essentially impossible to do what you're describing with wallets especially.
Glad it's helpful!
Hello @tight gulch, this is Nicholas. I am new to this channel, so I don't know how I can post a new chat. Would you mind if I ask a question regarding Stripe tax? Thank you in advance.
@desert perch looks like you're in the wrong place, this thread is for someone else's question.
- If you have your own thread, please chat there.
- If you don't have your own thread, use one of the buttons in https://discord.com/channels/841573134531821608/842637025524842496 to get help.
- Note: we don't reopen closed threads.
Posting inappropriate messages in other people's threads is against the rules. No worries if this was just an honest mistake, but if you violate the rules multiple times you will be removed from this server.
@desert perch go to the #help channel and click on an icon and it will submit a thread for you
They were able to create their own thread, thank you for helping them! ๐