This is a trending topic on Automation testing for E2E web applications.
Now, new guy in town Cypress does not use Selenium and runs directly in your app without any json wire protrocol, but it does not support parallel testing or mobile testing.
Have you experienced both? Should I stick with old and known ?
#testing cypress #selenium qaautomation #qa
We use Cypress because it's made browser testing simple and fast. The speed of both writing and executing the tests means that we're able to gain good coverage with minimal effort.
By building out browser tests we've been able to refactor large parts of the application and have a good degree of faith that everything is working. Next step is going to be adding Percy into the mix.
When I saw the founders of Cypress introduce it in some conference I knew I found the tool we needed to start writing E2E testing. What I like about it is that it provides a comprehensive solution for the whole lifecycle of writing E2E tests for your application, from the API you need to write the tests to showing you why they fail. It's also nice that other tools/services in the testing space, like Percy, integrate with them now.