Cypress vs WebdriverIO: What are the differences?
What is Cypress? Better, faster, and more reliable testing for anything that runs in a browser. Cypress is a front end automated testing application created for the modern web. Cypress is built on a new architecture and runs in the same run-loop as the application being tested. As a result Cypress provides better, faster, and more reliable testing for anything that runs in a browser. Cypress works on any front-end framework or website.
Some of the features offered by Cypress are:
- Time Travel
- Automatic Waiting
On the other hand, WebdriverIO provides the following key features:
- Support for the WebDriver specification as well as to Appium
- Easy Test Setup
Cypress and WebdriverIO are both open source tools. Cypress with 13.8K GitHub stars and 718 forks on GitHub appears to be more popular than WebdriverIO with 5.1K GitHub stars and 1.47K GitHub forks.
CircleCI, Intuit, and RELEX Solutions are some of the popular companies that use Cypress, whereas WebdriverIO is used by SuperAgendador.com, Soluto, and Shelf. Cypress has a broader approval, being mentioned in 88 company stacks & 112 developers stacks; compared to WebdriverIO, which is listed in 9 company stacks and 12 developer stacks.
In the company I will be building test automation framework and my new company develops apps mainly using AngularJS/TypeScript. I was planning to build Protractor-Jasmine framework but a friend of mine told me about Cypress and heard that its users are very satisfied with it. I am trying to understand the capabilities of Cypress and as the final goal to differentiate these two tools. Can anyone advice me on this in a nutshell pls...
I've used both Protractor and Cypress extensively. Cypress is the easier and more reliable tool, whereas Protractor is the more powerful tool. Your choice of tool should depend on your specific testing needs. Here are some advantages and disadvantages of each tool:
More reliable (tends to throw fewer intermittent false failures)
Easier to read code (handles promises gracefully)
Cannot switch between browser tabs
Cannot switch to iFrames
Cannot specify clicks or keypresses explicitly as if a real user was interacting
Cannot move the mouse to specific co-ordinates
Sometimes has trouble switching between different top-level domains, so not good for testing external links
Cypress is a newer tool with less extensive documentation and less community support
More powerful because it is Selenium-based - it can switch between tabs, it can handle external links to other domains, it can handle iFrames, simulate keypresses and clicks, and move the mouse to specific co-ordinates within the browser.
More extensive community support and documentation
Slower and more brittle - in general there is a higher likelihood of cryptic and/or intermittent errors which may cause your tests to fail even though there is nothing wrong with your application
For highly experienced automation engineers, the fundamental "brittle" nature of Selenium can be worked around - it can be reliable but only if you really know what you are doing
Less graceful handling of promises - relies on async/await or .then to manage the order of execution. Therefore it is a bit harder to read the code.
Harder to set up, and the method of setup impacts its reliability. For example, a hub/node configuration where the selenium jar is on a different physical machine than the browser under test will cause unreliability in your tests. Not everyone knows about this type of thing, so it's common to find Selenium frameworks that are set up poorly.
It's probably better to use Cypress if
you're at a smaller company and have a close relationship with developers who can help write hooks or stubs in their code to assist your testing
you don't need to do things like switch between tabs or test links to external top-level domains
It's probably better to use Protractor if
You might need to switch between tabs or test external links to other domains within the scope of your framework
You want to use a more accurate simulation of how a real user interacts with a browser (i.e. click at this location, type these keys)
You're at a company where you won't have any support from developers in writing hooks or stubs to make their code more testable in a less powerful framework like Cypress
Please try Handow, the e2e tool basing on Puppeteer.
Gherkin syntax compatible
Chrome/Chromium orentied, driven by Puppeteer engine
Create test suites rapidly without coding (or a little bit), basing on built-in steps library
Schedule test with plans and arrange stories with sequential stages
Fast running, execute story groups in parallel by multi-workers
Built-in single page report render
Cover page view, REST API and cookies test
we are having one web application developed in Reacts.js. in the application, we have only 4 to 5 pages that we need to test. I am having experience in selenium with java. Please suggets which tool I should use. and why ............................ ............................ .............................
Hi, I am starting out to test an application that is currently being developed - FE: React. BE: Node JS. I want the framework to be able to test all UI scenarios (from simple to complex) and also have the capability to test APIs. I also need to run tests across all OSs and Browsers (Windows, Mac, Android, iOS). I have also looked into react-testing-library and @TestProject.io. Any advice you can give as to which framework would be best and why would be so much appreciated! Thank you!!
You should also definitely look into Playwright, which is a new automation tool from Microsoft building on top of the Puppeteer experience and trying to bring this experience in the cross browser space - very exciting project. Great team. Also CodeceptJS as already Playwright support which at a ton of valuable features on top of Playwright, give it a go!
I'm also looking for the same, FE: React & BE: NodeJS. Cypress won't help as it lacks cross-browser testing, it doesn't support all the browsers. I'm still investigating it, but looks like WebdriverIO may fulfil what I'm looking for - Cross-browser testing, integration with CI/CD, running it as a docker service, good support on assertions & reporting of test results. Let me know if you found any information on any of the above mentioned points.
Hi Esther, if you really need cross OS and cross device automation Cypress wont help, with WebdriverIO you can do it … and check out CodeceptJS, which is a wrapper around several frameworks (like WebdriverIO) and will support future players (currently for example upcoming Playwright) as well.
As we all know testing is an important part of any application. To assist with our testing we are going to use both Cypress and Jest. We feel these tools complement each other and will help us get good coverage of our code. We will use Cypress for our end to end testing as we've found it quite user friendly. Jest will be used for our unit tests because we've seen how many larger companies use it with great success.
Sign up to add or upvote prosMake informed product decisions
Sign up to add or upvote consMake informed product decisions
What is Cypress?
What is WebdriverIO?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions