mabl vs. WebdriverIO

We haven't found a scenario yet where it hasn't been appropriate. We did have one function on our application that mabl couldn't do, but they solved it and got back to us very quickly. Our application is web-based and mabl is able to handle this very easily. We use the command line runner a lot. Being able to easily and quickly change from a cloud based run to a local run has been fantastic. Setting up flows and environments is a wonderful feature

Incentivized

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!

Incentivized

• mabl trainer - record and play back test cases
• Organization - labels and flows make this easy
• Customer support!

Incentivized

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

Incentivized

• Asserts could be easier to add, but they aren't terribly hard

Incentivized

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

Incentivized

We ultimately selected mabl cause it most met our needs and our budget. We needed a low code UI automation test tool. We also have a suite of existing testing tools and other tools that it needed to be able to integrate with. Price was the only thing that ruled out some of the above tools, we are a small start up, and don't have a huge budget. Some tools listed didn't have the same functionality or ease of use with the record and playback. mabl works on our machines and integrates with our existing tools

Incentivized

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

Incentivized

• We are able to more quickly automate UI tests

Incentivized

• 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

Incentivized