Skip to main content
TrustRadius
WebdriverIO

WebdriverIO

Overview

What is WebdriverIO?

WebdriverIO, an OpenJS Foundation project, is a next-gen browser and mobile automation test framework for Node.js. It can be run on the WebDriver Protocol for true cross-browser testing as well as Chrome DevTools Protocol for Chromium based automation using Puppeteer.

Read more
Recent Reviews

WebdriverIO

8 out of 10
January 21, 2022
Incentivized
For automating the web browser and native mobile applications we use WebdriverIO in my organization. WebdriverIO supports javascript and …
Continue reading

WebdriverIO

8 out of 10
January 11, 2022
Incentivized
Used WebdriverIO in our Automated Test Replaced our Manual test for Regression Testing & Pre-release testing Help QA team build knowledge …
Continue reading
Read all reviews
Return to navigation

Product Demos

Demo cross browser testing with webdriverIO + Cucumber

YouTube

Demo: Continuous local WebdriverIO testing with 'onchange' and 'node-notifier'

YouTube

Debug WebdriverIO automation tests using Visual studio code

YouTube

WebdriverIO How to implement Page Object Model

YouTube
Return to navigation

Product Details

What is WebdriverIO?

WebdriverIO Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(9)

Reviews

(1-5 of 5)
Companies can't remove reviews or game the system. Here's why
Chris Hyde | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
We needed to find a solution for SaaS-based browser automation for a client of ours. Looking for a lightweight, easy-to-use tool that has all the integrations we need, and WDIO is that. It even has a great startup script that sets up most of those for you! Very easy to deploy and robust community support makes it simple to get going.
  • numerous integrations to tools
  • fast easy location of page elements
  • tool setup is amazing - they have a script to walk you through everything with prompts!!
  • integrations with reports (specifically allure) frameworks could be easier
I haven't seen a use case that WDIO can't cover, even including integrations into performance/load testing and mobile! The fact that there are boilerplate projects and code examples galore make it so simple to understand and see real-world PoCs of concepts you need to understand. I highly recommend WDIO!
  • Ease/speed of development
  • Integrations
  • Robust feature set
  • Haven't implemented in a live project yet
Stands out as a clear leader. The fact that there are so many integrations and the simplicity of writing code should make you want to select WebdriverIO. However, the full-feature nature of this framework is what sets it apart. I hope to be able to get this framework going soon!
January 21, 2022

WebdriverIO

Score 8 out of 10
Vetted Review
Verified User
Incentivized
For automating the web browser and native mobile applications we use WebdriverIO in my organization. WebdriverIO supports javascript and also is open-source which is very beneficial for the user. Basically, we use WebdriverIO for automating the ios application and It is very easy to use and also very easy to learn.
  • Automating Browser
  • Automating ios native application
  • Support javascripts
  • Only support Java scripts
  • Should support more languages
  • NA
When we are working on an automation project and we want to automate the ios application then WebdriverIO is the best solution to do the same. It is very useful to automate the ios app and also one good thing is it is open-source. we can automate both app and browser using this.
  • Supports App and browser both
  • addCommand function
  • Integrates Jenkins
  • Frame supports
  • Integration for Jenkins
  • Only support JavaScripts
Anurag Bharti | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
We are using webdriverIO with typescript. We are using Reactjs for Front-end development. Our use-case is to automate multiple live sessions for different users like Teachers, Student, etc. So we have WebdriverIO for browser testing. I would like to test with WebdriverIO as we can select the way we like to interact with the browser whether it's web driver or DevTools. This is a framework that has a command-line interface (CLI) and a very flexible configuration.
Advantages I feel over other tools:
1.Easy project setup.
2.Flexible configuration.
3.Integration with other test automation tools out of box.
  • It allows to automate any application written with modern web frameworks such as React
  • It can be used to automate native mobile applications for Android and iOS.
  • The WebdriverIO testrunner comes with a command line interface that provides a nice configuration utility that helps to create config file in a minute.
  • It can run the commands both in sync and async modes.
  • It provides a set of commands that abstract away common interactions with an application like navigating, clicking, reading the state of an element.
  • Tasks written in this can only be debugged using the provided WDIO task runner
  • We cannot set breakpoints within tasks but have WDIO pause the run between commands.
  • It is not as customized as Protractor.
  • It deviates from generic syntax which may confuse Selenium developers having knowledge of other languages.
Best suited where frontend developments are in React and where BDD and TDD test frameworks are to be used. Its syntax is very easy to write and understand. Even the non-programmer can do the initial setup.

Not suited when the language you are using is other than Javascript(or Typescript).
  • It has excellent API documentation
  • It has support for most BDD and TDD test frameworks.
  • It has a command-line interface-wdio which makes test configuration easy and simple.
  • It helped in cross browser testing
  • It helped in automating multiple browsers at a time.
  • Code coverage is optimum as this supports Javascript(Typescript)
1. WebdriverIO is used for automating both browsers and native mobile apps.
2. Selenium is being used on most of the languages except JavaScript (TypeScript) and our front-end development is in Reactjs
January 11, 2022

WebdriverIO

Score 8 out of 10
Vetted Review
Verified User
Incentivized
Used WebdriverIO in our Automated Test Replaced our Manual test for Regression Testing & Pre-release testing Help QA team build knowledge in Automation using Selenium and WebdriverIO Framework.
  • Quick start when running the test, easy to maintain the framework.
  • Faster and has vast community support on the internet.
  • No need to Build an Automation framework from scratch.
  • Can be integrated with different services.
  • Standalone Report or logging could be useful.
  • Not integrated with AIO Test management tool from Atlassian.
WebdriverIO only works on specifically on web, you have to create a workaround when handling features like uploading or downloading files into your application. Other than that, WebdriverIO is easy to use.
  • Maintainability.
  • Can be integrated with Docker.
  • Runs on multiple Browsers and in Multiple environments.
  • Can be integrated with different third-party report generators.
  • Free and maintainability.
  • Easy to use and implement.
Other tools we selected don't work in our application, it does or doesn't support multiple frames or need more tweaking just to make it works. When testing out WebdriverIO it just works as expected, no need to do such walk around to make it works multiple frames. It also can handle multiple tabs and windows.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
We use WebdriverIO as a bridge between the tests for our games and Saucelabs and their VMs/Devices. Tests are written in Javascript where we then have a middle layer that handles getting to the games on a browser to then execute those written tests. This way, test writers do not need to know how to trigger the tests on the devices they need and just specify it through parameters. WebdriverIO is used as the interface that takes these parameters and then launches the tests to Saucelabs
  • Most parameters are input in one place (wdio.conf)
  • Tests can be organised using a separate test execution framework like Mocha
  • Easy typescript transition
  • wdio.conf can contain too much where everything is encapsulated there, like the before and after functions
  • A data provider-like testing would be useful. The only way to input different data into the same test is via a loop
  • everything is needed to be done using the 'browser' object. Can be limiting where you don't have access to the browser depending on where you are in the code
'Pros' Scenarios Those are new to javascript but may have a background with another language. It is super simple to get started up and most of your parameters needed are plugged in one place (wdio.conf file) 'Cons' Scenarios It was very fiddly to use data between the tests and the before/after functions. They are located in different places and needed a workaround to share data between the two places It's not elegant when creating data-driven test cases. Have to surround tests with a loop to then plug in the data needed
  • Easy integration with Saucelabs via sauce services
  • Easy integration with a separate test execution framework like jasmine or mocha - can pick and choose as needed
  • Gives easy access to Saucelabs Devices and VMs to the frontend developers who don't have to fiddle around with connection to Saucelabs itself - so ROI on Saucelabs as webdriverIO is free
  • The small learning curve to actually get set up and running - our working framework was written in a few days
Was missing a few from the list, but we also tried: Jest Puppeteer Nightwatch.js Webdriver.js Webdriver.io compared to the above ticked more boxes. Some of the things we looked for: Async/sync support Popularity within the community Support for screenshots Access to Dev tools Ability to run locally Support for BDD Ability to use Saucelabs Multiple browser sessions Headless browser support
Return to navigation