Mobile Test Automation – Appium – Part I
Appium is an open source test automation framework for use with native, mobile web and hybrid mobile app. I found couple of interesting articles regarding this and it kept me excited, so I’ve decided to take a look.
Before going in to the configuration section, let’s just go through how Appium developed and the basic pillars of the Appium.
Appium is a cross-platform tool, it allows you to write tests against multiple platforms (iOS/Android/ Windows) using the same API. Also it enables the code reuse between iOS / Android platforms. You shouldn’t have to recompile your app / or modify it in any way in order to automate it. Appium use the vendor provided frameworks from the main vendors who produces mobiles such as Apple / Google / Windows.
- You shouldn’t have to recompile app / or modify in in any way in order to automate it – Appium use the vendor provided frameworks from the main vendors who produces mobiles such as Apple / Google / Windows. So we don’t need to compile any Appium specific or third party code to the app.
- You shouldn’t be locked into specific language/ or framework to write and run your tests. – Appium wraps the vendor provided frameworks in one API (Web Driver API – Selenium Web Driver ) This specifies the client- server architecture, a client written any language can be used to send HTTP requests to the server.
- A mobile automation framework shouldn’t reinvent the wheel when it comes to automation APIs. – WebDriver has the standard for automating web browsers, it has extend the protocol with extra API methods which can be used to mobile automation
- A mobile automation framework should be open source, in spirit and practices as well as in name. – Appium is an open source project
More on configuration later 🙂