Need advice about which tool to choose?Ask the StackShare community!


+ 1

+ 1
Add tool

WebdriverIO vs Playwright: What are the differences?

What is WebdriverIO? Webdriver/Selenium 2.0 JavaScript bindings for Node.js. WebdriverIO lets you control a browser or a mobile application with just a few lines of code. Your test code will look simple, concise and easy to read.

What is Playwright? Node library to automate Chromium, Firefox and WebKit with a single API (By Microsoft). It is a Node library to automate the Chromium, WebKit and Firefox browsers with a single API. It enables cross-browser web automation that is ever-green, capable, reliable and fast.

WebdriverIO and Playwright can be categorized as "Browser Testing" tools.

Some of the features offered by WebdriverIO are:

  • Extendable
  • Support for the WebDriver specification as well as to Appium
  • Easy Test Setup

On the other hand, Playwright provides the following key features:

  • Node library
  • Headless supported
  • Enables cross-browser web automation

WebdriverIO and Playwright are both open source tools. Playwright with 10.9K GitHub stars and 282 forks on GitHub appears to be more popular than WebdriverIO with 5.58K GitHub stars and 1.63K GitHub forks.

Advice on Playwright and WebdriverIO
Needs advice

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 ............................ ............................ .............................

See more
Replies (1)
Prashanth Marappa
Senior Software Engineer at Mphasis · | 1 upvotes · 201.8K views

with the help of selenium we can automate react js for functional testing

See more
Needs advice

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 Any advice you can give as to which framework would be best and why would be so much appreciated! Thank you!!

See more
Replies (3)

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!

See more
Jinesh Khimsaria
Test Automation Specialist at Personal · | 3 upvotes · 68.6K views

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.

See more

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.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Playwright
Pros of WebdriverIO
  • 13
    Cross browser
  • 10
    Open source
  • 9
    Test Runner with Playwright/test
  • 7
    Well documented
  • 7
    Promise based
  • 5
    Execute tests in parallel
  • 5
    API Testing
  • 5
    Integrate your POMs as extensible fixtures
  • 4
    Python Support
  • 4
    Capture videos, screenshots and other artifacts on fail
  • 3
    Context isolation
  • 3
    Inbuild reporters html,line,dot,json
  • 1
  • 11
    Various integrations to vendors like Sauce Labs
  • 10
    Open Source
  • 8
    Great community
  • 7
    Easy to setup
  • 4
    Best solution for broad browser support

Sign up to add or upvote prosMake informed product decisions

Cons of Playwright
Cons of WebdriverIO
  • 12
    Less help
  • 3
    Node based
  • 2
    Does not execute outside of browser
  • 8
    High maintenance

Sign up to add or upvote consMake informed product decisions

What companies use Playwright?
What companies use WebdriverIO?
See which teams inside your own company are using Playwright or WebdriverIO.
Sign up for StackShare EnterpriseLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Playwright?
What tools integrate with WebdriverIO?

Sign up to get full access to all the tool integrationsMake informed product decisions

What are some alternatives to Playwright and WebdriverIO?
Puppeteer is a Node library which provides a high-level API to control headless Chrome over the DevTools Protocol. It can also be configured to use full (non-headless) Chrome.
Selenium automates browsers. That's it! What you do with that power is entirely up to you. Primarily, it is for automating web applications for testing purposes, but is certainly not limited to just that. Boring web-based administration tasks can (and should!) also be automated as well.
Protractor is an end-to-end test framework for Angular and AngularJS applications. Protractor runs tests against your application running in a real browser, interacting with it as a user would.
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.
It is a pure node.js end-to-end solution for testing web apps. It takes care of all the stages: starting browsers, running tests, gathering test results and generating reports.
See all alternatives