3 ms·

> That in itself isn't a problem but Cypress seems strongly designed around the idea that you never leave the domain. Same here with PayPal or 3d-secure. I am

> That in itself isn't a problem but Cypress seems strongly designed around the idea that you never leave the domain. Same here with PayPal or 3d-secure. I am actually baffled by the decision - what kind of applications did they thought was going to get tested - Todo apps? Last I checked there was GH issue and they said that it will get addressed, I hope. What they are also saying is that it is bad practice, you should send API requests from the tests that simulate the payment, for example. I find this BS, IMO the automation tests simulate user and user would not send API requests but click buttons on the screen.

spondyl 6y ago
In the particular case I mentioned above, it seemed the recommended avenue was to do sign in on the backend so you could mock it out. Sounds fine on paper but in our case, we called out to multiple backends, with no unifying gateway that traffic reached them through as they were owned by different teams. Realistically, that was a discipline issue rather than a technical issue of course but I do wonder how many organisations find tools like Cypress a non-starter due to their impure set up