WebdriverIO Reviews and Ratings

Use Cases and Deployment Scope

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.

Likelihood to Recommend

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!

Use Cases and Deployment Scope

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.

Likelihood to Recommend

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.

Use Cases and Deployment Scope

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.

Likelihood to Recommend

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

Use Cases and Deployment Scope

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.

Likelihood to Recommend

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.

Use Cases and Deployment Scope

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

Likelihood to Recommend

'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