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.
N/A
Pricing
WebdriverIO
Editions & Modules
No answers on this topic
Offerings
Pricing Offerings
WebdriverIO
Free Trial
No
Free/Freemium Version
No
Premium Consulting/Integration Services
No
Entry-level Setup Fee
No setup fee
Additional Details
—
More Pricing Information
Community Pulse
WebdriverIO
Considered Both Products
WebdriverIO
Verified User
Consultant
Chose WebdriverIO
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 …
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!
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
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 …
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).
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
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.