Appium is an open source test automation tool for native and hybrid mobile apps. It supports both iOS and Android. Appium drives Apple's UIAutomation library and Android's UiAutomator using Selenium's WebDriver JSON wire protocol. Appium is based on Dan Cuellar's work on iOS Auto.
Testing with Appium has two big benefits:
You don't have to recompile your app or modify it in any way, due to use of standard automation APIs on all platforms.
> Mac OS X 10.6 or higher > XCode > Apple Developer Tools (iPhone simulator, command line tools) > Android SDK API >= 17 > Node and npm (http://www.nodejs.org) (Node must be >= v0.8)
Get something working with a quickness.
> mkdir appium-test && cd appium-test > sudo npm install appium -g > npm install wd > curl -O https://raw.github.com/appium/appium/master/sample-code/examples/node/simplest.js > appium & > node simplest.js
We support a sub-set of the Selenium WebDriver JSON Wire Protocol.
We also have several extensions to the JSON Wire Protocol for automating mobile gestures like tap, flick, and swipe.
You can also automate web views in hybrid apps! See the hybrid app guide
We support Android and iOS platforms side-by-side:
- Set up your system for Appium iOS support
- Set up your system for Appium Android support
- Prepare your app for an iOS test
- Prepare your app for an Android test
- Run an iOS test
- Run an Android test
- Getting started with Appium and Ruby on OS X
Install node.js (includes npm, the node.js package manager).
Fork the Appium repo ( https://github.com/appium/appium ), then clone your fork.
From your local repo clone's command prompt, install these packages using the following commands:
> sudo npm install -g mocha > sudo npm install -g grunt-cli > npm install
The first two commands install test and build tools (sudo may not be necessary if you installed node.js via Homebrew). The third command installs all app dependencies.
(First, have a look at setting up your system for Appium iOS support.)
To avoid a security dialog that may appear when launching your iOS apps you'll
have to modify your
/etc/authorization file in one of two ways:
Manually modify the element following <allow-root> under <key>system.privilege.taskport</key> in your
/etc/authorizationfile to <true/>.
Run the following grunt command which automatically modifies your
/etc/authorizationfile for you:
sudo grunt authorize
Important Note: Making this modification to your
grants access privileges to all members belonging to your
Download the UICatalog test app:
> grunt downloadApp
Build the test apps (if the functional tests fail, try running these grunt commands again):
> grunt buildApp:UICatalog > grunt buildApp:TestApp > grunt buildApp:WebViewApp
(First, have a look at setting up your system for Appium Android support.)
Configure the and build bootstrap .jar:
> grunt configAndroidBootstrap > grunt buildAndroidBootstrap
Configure and build the test app:
> grunt configAndroidApp:ApiDemos > grunt buildAndroidApp:ApiDemos
Make sure you have one and only one Android emulator or device running, e.g.
by running this command in another process (assuming the
emulator command is
on your path):
> emulator -avd <MyAvdName>
Since we use dev versions of some packages, it often becomes necessary to install new NPM packages or update various things. There's a handy shell script to do all this:
Once, your system is set up and your code is up to date, you can run all the functional tests:
> grunt functional
Note: we use wd as the Selenium client in our functional tests. Because of the work we are doing to extend the WebDriver protocol, we use the development version of wd. If you've installed wd in some other way, you might need to do this in the Appium project directory to get the tests to run successfully:
> rm -rf node_modules/wd > npm install .
Run unit tests:
> grunt unit
Run all tests:
> grunt test
Before committing code, please run grunt to execute some basic tests and check your changes against code quality standards:
> grunt Running "lint:all" (lint) task Lint free. Done, without errors.
If you want to run the Appium server and have it listen indefinitely, you can execute one of the following commands to start an Appium server with or without a specified app:
> grunt appium // launch Appium server without app > grunt appium:TestApp // launch Appium server with the TestApp > grunt appium:UICatalog // launch Appium server with the UICatalog app
Like the power of automating dev tasks? Check out the Appium grunt tasks available to help with building apps, installing apps, generating docs, etc...
If you have an Appium server listening, you can run individual test files using Mocha, for example:
> mocha -t 60000 -R spec test/functional/testapp/simple.js
Do you like getting close to the metal? Or are you trying to launch an Appium server from a script with a custom app? If so you can start Appium without grunt from the command line with an app or without an app, among other things:
> node server.js -V // launch Appium server without app > node server.js --app /absolute/path/to/app -V // launch Appium server with app > node server.js --launch // pre-launch the app when appium loads > node server.js --log /my/appium.log // log to file instead of stdout > node server.js --warp // use unsupported system-crashing speedup tech
(See the server documentation for all CLI arguments.)
Using with a Bitbeambot
AWAITING THE FUTURE
Fork the project, make a change, and send a pull request!
Oh and please have a look at our Style Guide before getting to work.
The open source community has made this project possible, please add missing projects to the list.
Announcements and debates often take place on the Discussion Group, be sure to sign up!