Robot Framework vs. WebdriverIO

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Robot Framework
Score 7.0 out of 10
N/A
Robot Framework is a generic keyword-driven test automation and RPA framework for acceptance level testing and acceptance test-driven development (ATDD).N/A
WebdriverIO
Score 9.0 out of 10
N/A
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
Robot FrameworkWebdriverIO
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Robot FrameworkWebdriverIO
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
Robot FrameworkWebdriverIO
Considered Both Products
Robot Framework

No answer on this topic

WebdriverIO
Chose WebdriverIO
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!
Chose WebdriverIO
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
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 …
Chose WebdriverIO
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 Alternatives
Robot FrameworkWebdriverIO
Small Businesses
BrowserStack
BrowserStack
Score 8.6 out of 10
BrowserStack
BrowserStack
Score 8.6 out of 10
Medium-sized Companies
ReadyAPI
ReadyAPI
Score 7.0 out of 10
Selenium
Selenium
Score 8.1 out of 10
Enterprises
ignio AIOps
ignio AIOps
Score 8.1 out of 10
Selenium
Selenium
Score 8.1 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Robot FrameworkWebdriverIO
Likelihood to Recommend
5.0
(0 ratings)
9.0
(0 ratings)
User Testimonials
Robot FrameworkWebdriverIO
Likelihood to Recommend
It suits for checking features of a simple web application or features that don't heavily rely on AJAX. You could create tests that check if application is running properly and raise alarm if required so someone can manually check for problems. However making big test sets to produce reliable results may prove to be difficult or impossible. Also running lots of test cases can take hours.
Read full review
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!
Read full review
Pros
No answers on this topic
  • 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.
Read full review
Cons
No answers on this topic
  • 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.
Read full review
Alternatives Considered
No answers on this topic
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
Read full review
Return on Investment
No answers on this topic
  • 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
Read full review
ScreenShots