#alisa_87774
1 messages · Page 1 of 1 (latest)
Hello! The general recommendation is to not use end-to-end testing libraries with our payment UIs
Instead you should just be stubbing responses
Hi. Thanks for getting back. Could you please be little more specific about why to not use it? Thanks
A few reasons really. Predominantly that we could change our markup/HTML in our hosted UIs without any notice to you which would break your tests
Also, not sure what it is you're trying to test exactly. Should be sufficient for you to test that the user is redirected
This is the test step: 1. Click the button Subscribe on the application- this will lead to the stripe checkout page 2. Verify redirection (stripe url) . But as soon as the stripe checkout page is opened, chromedriver does not respond. So simple action like driver.getUrl() does not work at all. For that reason, I wonder if there are some limitations and restrictions that prevent chromedriver to access the checkout page.
Interesting part is that it will work sometimes.