SDET Unicorns

Cypress vs WebdriverIO | Which one to pick?

Table of Content

In this article, I will go over one of the most common questions that I get asked and that is – what is the difference between Cypress & WebdriverIO and which one should you pick? We will cover everything from top features, to framework limitations to browser support and a lot more…

Language Support & Popularity

Language SupportJavaScript / TypeScriptJavaScript / TypeScript
GitHub Stars~38K~7.5K
Downloads (npm)~3.5M~1M
Releases1-2 weeksWeekly
  • Both Cypress & WDIO supports JavaScript / TypeScript languages
  • In terms of popularity, Cypress is doing bit better than WDIO as per GitHub stars and NPM downloads
  • Both Cypress & WDIO are actively maintained with weekly / bi-weekly releases

Key Features

Beginner friendly setupBeginner friendly setup (customizable)
Tests are easy to read & understandTests are easy to understand for JS users 
Not dependent on Selenium WebdriverUses custom implementation of Webdriver
Interactive test runnerCLI test runner only
Built-in wait and retriesBuilt-in wait and retries
API testing supportedNeed external libraries
  • Both Cypress and WDIO have pretty straightforward setup. Although, with WDIO you get lot more customization option when setting up your project
  • Cypress tests are more readable when compared to WDIO. WebdriverIO async-await syntax can be confusing for non-JS users
  • One of the unique things with Cypress is that it has no dependency with Selenium Webdriver making it more faster and stable vs WebdriverIO uses custom implementation of the Webdriver APIs
  • Cypress comes with an interactive test runner which is quite user friendly and of the most loved features of it. On the other hand, WDIO uses CLI test runner like many other frameworks
  • Both Cypress and WDIO have built-in wait and retry functionality when searching for elements on DOM
  • With Cypress, you have built-in API testing support vs with WDIO you can set it up with external library


Limited browser supportAsync-await syntax can be confusing for beginners
Cross-origin restrictionsDifficult to debug tests
Multi-tab and multi-window not supportedNo paid features
Built-in parallelization not supportedLots of customization can be overwhelming
Not as customizable


  • One of the major limitations of Cypress is limited browser support (will go over this in detail later in the article)
  • With Cypress, each individual test can run on single super domain only i.e you cannot access and within same test.
  • Cypress does not support multi-tab or multi-browser at the same time
  • While Cypress supports parallelization, it is part of their paid plan. Free option only has limited no. of runs
  • Cypress in general is not as customizable compared to WDIO (some of this is also intentional to make it beginner friendly)


  • With new WebdriverIO changes, you need to write tests using async-await which can be confusing for beginners
  • It’s bit difficult to debug WebdriverIO tests compared to Cypress
  • WebdriverIO is fully open-source projects and does not provide any paid features or support
  • While WebdriverIO does support lots of customization options, it might get overwhelming for beginners to set everything up

Browser Support

Supports Chromium family (Chrome, Edge, Electron, Brave) and FirefoxSupports all major browsers (Chrome, Firefox, Edge, IE and Safari)
  • As mentioned earlier, one of the major drawbacks currently with Cypress is that it does not support Safari. It supports all the major browsers though.
  • On the other hand, WebdriverIO has support all major browsers including which is one of key reasons to pick WebdriverIO over Cypress

Native Mobile Support

No support 🙁Possible using Appium
  • Cypress is built only for Web and will not have any support for native apps on the other hand WebdriverIO can be easily integrated with Appium to automate Mobile apps.
  • If you are interested in learning WebdriverIO with Appium, feel free to checkout my course on Udemy

Technical Differences

Locators SupportCSS Selector, (XPath plugin)CSS, XPath
iFrame SupportDifficult to work withEasy to switch to iFrame
Shadow DomSupportedSupported
Network InterceptionBuilt-inConfigurable
Google LighthouseExternal PluginBuilt-in (DevTools Service)
  • Cypress has default support for CSS Selectors but can work with Xpath using external plugin. WDIO supports both CSS and XPath by default
  • Due to cross origin restrictions, its difficult to work with iFrames in Cypress. On the other hand, with WDIO it’s fairly easy to switch to iFrames
  • Both Cypress and WDIO has support for Shadow DOMs
  • Cypress has built-in support for network interception and with WDIO it is configurable with an external service
  • WDIO has built-in Google lighthouse integration for performance report using DevTools service and for Cypress, you can do the same with an external plugin

Miscellaneous differences

Test FrameworkMocha, Cucumber (external)Mocha, Jasmine, Cucumber
ParallelizationPossible with paid planBuilt-in
ReportersSpec, Mocha, CustomSpec, Allure, Report Portal, etc.. 
CI/CDPossible with major CI/CDPossible with major CI/CD
DocumentationIntuitive and OpinionatedGood documentation
Community SupportGrowing CommunityDecent Community Support
  • Cypress only support Mocha test framework but does have support for Cucumber as an external plugin. WDIO on the other hand supports Mocha, Jasmine and Cucumber built-in
  • Parallelizing tests with Cypress is possible with paid plan only but with WDIO its built-in and free
  • Cypress supports Spec, Mocha and Custom reporting and WDIO supports bunch of reporters such as Spec, Allure, Report Portal etc..
  • Both Cypress and WDIO can be easily integrated with major CI/CD tools
  • In terms of documentation, Cypress docs are really intuitive and beginner friendly. With WDIO, you get decent documentation but can be confusing for beginners
  • Cypress has a growing community and is quite active on Github and Gitter. Similarly, WDIO has a good community support as well active on both Github and Gitter

Which one to pick?

So that was all the major differences and similarities between Cypress and WebdriverIO. Now the question is which one to pick for your next automation project? Well the answer is – It Depends

What you should rather be asking is – What are the requirements? Understand the requirements first.

For example, if the requirement is to run tests in Chrome and Safari as that’s where the majority of the users are then probably it’s better to go with WebdriverIO. Or, may be you one suite for Web and Mobile, then again it’s a better choice to go with WebdriverIO.

On the other hand, if the requirement, is to execute tests on chromium based browsers only and you need a good dashboard that can give you an overview of all your tests, then probably its better to go with Cypress if the team is ok to go with a paid option.

To conclude, both frameworks are great and have their own pros/cons but its up-to you to look at what exactly you need for your next automation project based on your project requirements and then make a decision accordingly by referring to this article.

To learn more in detail about the differences and similarities between Cypress and WebdriverIO, checkout this video –

If you are interested in learning more about WebdriverIO, then checkout my courses on Udemy below –

My Resources

Thrive Suite: The all-in-one WordPress theme I used to create my blog.
Jasper AI: My favorite AI writing tool.
Surfer SEO:  A tool to help you rank your content on the first page of Google.

Write Content Faster


Write blog posts that rank for affiliate terms!

Join our mailing list

Unlock the Secrets to Becoming a SDET Pro in the Industry!

Stay ahead of the curve! Join our mailing list for exclusive insights, tips, and the latest industry updates delivered straight to your inbox

Table of Content

Related Post

Differences Between CI/CD and DevOps

Key Differences Between CI/CD and DevOps

Software development is far from a simple journey that involves merely executing code and launching applications. It often presents challenges, as it’s rare to get everything right from the start. Each time you implement new or frequent code changes, you inadvertently introduce potential issues that can be time-consuming to resolve. This complexity necessitates a structured approach to ensure smooth production.

Read More »

Common Types of Software Bugs

Dealing with bugs is one of the biggest headaches in the software development lifecycle. No matter how carefully someone writes code, it’s impossible to create a software product that works perfectly every time. Skipping detailed testing often causes major issues later on.

Read More »