Appium vs. WebdriverIO

Appium works well for well-structured mobile applications test automation that is particularly easy to leverage when different pages of the app use similar building blocks. If it takes time for some content in the app to be rendered, ask your dev team to add progress indicators and ensure they are accessible. That might be more complicated to do with Appium, though, if there's no good contact with Dev team established so you can request accessibility IDs added quickly enough when needed. Appium supports another locator strategies as well though (such as xPath or iOS class chain on iOS) but they wouldn't work as fast so you may get really slow tests.

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

• Crossdevice: With Appium you can automate tests for Android and iOS both. There is no need to learn more than 1 language.
• Easy: It's really easy to configure and use appium; it's very useful when you're testing strategy is based on "developers write tests".
• Open Source: It's such a nice strength of appium, because you don't need to pay to use a good tool like Appium is.

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

• There are a number of expected methods that are not implemented, yet. With a similar sounding name as Selenium with similar functions, people who are familiar with Selenium try to use methods that appear to be available, but give a "not yet implemented" exception when run.
• Documentation can be confusing.
• Setup was a difficult process. This may not necessarily be the case once you figure everything out, but the whole figuring it out process was difficult and I ran into many, many problems when I first started.

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

I am rating 10/10 because Appium can use with multiple programming languages with multiple Test engines. Also, it works for both Android and iOS.

Incentivized

I would like to give 9/10 rating to Appium because of it can easily integrate with popular frameworks and CI/CD tools, as well as it is reliable, flexible and easy to use. The setup can bit complex in initial step, but once on configured it's very easy to use and enables stable and scalable mobile automation for real and cloud devices.

Incentivized

Most of mobile testing tools which are available in the market are paid license tools. But Appium is Open source mobile testing tool. We can create customised automation framework using Appium. It also supports various languages such as Java, Javascript etc. And also supports various operating systems such as Android, IOS etc. We can easily integrate Appium frameworks with CI/CD [Jenkins, Git etc].

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

• For cost of ownership, the increase is positive times infinity, as it's free to install and use
• Lead time for suite development can be a negative, if not planned for during sprint planning
• Using Appium to execute tests in parallel across a cloud solution can improve CI/CD cycles by 100's of a percent

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