πŸ“± Automation for iOS and Android Apps.
ΠŸΠ΅Ρ€Π΅ΠΉΡ‚ΠΈ ΠΊ Ρ„Π°ΠΉΠ»Ρƒ
bootstraponline 48e2260886 Update badges
Update npm version badge to svg
Add monthly appium npm downloads badge
Add pull requests badge
Add issues closed badge
Fix CloudBees build status badge
2015-04-16 21:59:38 -04:00
assets handle locale-setting responsibilities in-house instead of using deprecated ios-sim-locale (fix #3595) 2014-10-13 09:50:29 -07:00
bin remove xcode switching logic from bin/test.sh; the possible combos are too complex for test.sh to do a good job with 2015-04-15 12:27:32 -07:00
ci cleaning up old ci tools 2015-03-02 21:55:30 +08:00
docs Merge pull request #4941 from 0x1mason/memory_issue 2015-04-16 17:03:13 -04:00
lib Merge pull request #4942 from imurchie/isaac-ios-crashlogs 2015-04-16 14:58:13 -07:00
submodules Updating appium-uiauto 2015-04-15 16:15:52 -07:00
test Merge pull request #4942 from imurchie/isaac-ios-crashlogs 2015-04-16 14:58:13 -07:00
.gitignore ci fix 2015-02-28 20:39:46 +08:00
.gitmodules refactor of ios.js. Main launch sequence broken into separate flows for simulators and real devices. Added appium-xcode repo to replace xcode.js. Use idevice_id to get device udid, fallback on udidetect. Use idevicesyslog to get device logs, fallback on deviceconsole 2015-04-10 14:05:20 -07:00
.jscsrc adds Android api 18 to new ci 2015-02-23 12:27:22 +08:00
.jshintignore adds Android api 18 to new ci 2015-02-23 12:27:22 +08:00
.jshintrc disabling shelljs in jshint 2015-02-23 20:06:47 +08:00
.npmignore move all android-related files together into devices/android 2013-10-17 12:33:49 -07:00
AUTHORS add self to authors, fix spelling 2013-01-23 07:55:15 -08:00
CHANGELOG.txt 1.3.7 2015-03-24 11:56:19 -04:00
CONTRIBUTING.md get the running from source docs in our docs, not in CONTRIBUTING 2014-08-08 14:46:46 -07:00
Gruntfile.js Moving linting and unit tests to gulp, they can still be called via grunt 2015-02-06 23:28:28 +08:00
LICENSE Adding Apache2 license file 2013-02-04 11:58:46 -08:00
README.md Update badges 2015-04-16 21:59:38 -04:00
RELEASE.pdf Copying over release of rights from Zoosk for ios automation code used in Appium 2013-01-21 17:01:08 -08:00
grunt-helpers.js make sure authorize-ios doesn't fail if a dir happens to not exist (not a fatal error) 2015-04-15 12:07:11 -07:00
gulpfile.js increasing emulator wait timeout 2015-03-13 13:11:09 +08:00
install-beta.md added appium beta install doc 2014-11-24 18:51:38 +08:00
install-from-npm.md added install from npm doc 2014-12-01 15:42:48 -08:00
package.json Updating appium-uiauto 2015-04-15 16:15:52 -07:00
reset.bat move sample code and apps out of main repo 2014-08-12 17:58:42 -07:00
reset.sh refactor of ios.js. Main launch sequence broken into separate flows for simulators and real devices. Added appium-xcode repo to replace xcode.js. Use idevice_id to get device udid, fallback on udidetect. Use idevicesyslog to get device logs, fallback on deviceconsole 2015-04-10 14:05:20 -07:00
trigger.txt testing jenkins build trigger 2015-02-09 09:44:38 +08:00

README.md

Appium

NPM version Dependency Status devDependency Status

Monthly Downloads Pull Requests Issues Closed

Build Status

Appium is an open source, cross-platform test automation tool for native, hybrid and mobile web apps, tested on simulators (iOS, FirefoxOS), emulators (Android), and real devices (iOS, Android, FirefoxOS).

Note: we have just recently released Appium 1.0. If you already have a bunch of Appium tests, you might want to check out the Migrating to 1.0 doc!

Supported Platforms

  • iOS
  • Android
  • FirefoxOS

See the platform support doc for more detailed information.

Why Appium?

  1. You don't have to recompile your app or modify it in any way, due to use of standard automation APIs on all platforms.
  2. You can write tests with your favorite dev tools using any WebDriver-compatible language such as Java, Objective-C, JavaScript with Node.js (in promise, callback or generator flavors), PHP, Python, Ruby, C#, Clojure, or Perl with the Selenium WebDriver API and language-specific client libraries.
  3. You can use any testing framework.

Investing in the WebDriver protocol means you are betting on a single, free and open protocol for testing that has become a defacto standard. Don't lock yourself into a proprietary stack.

If you use Apple's UIAutomation library without Appium you can only write tests using JavaScript and you can only run tests through the Instruments application. Similarly, with Google's UiAutomator you can only write tests in Java. Appium opens up the possibility of true cross-platform native mobile automation. Finally!

I don't get it yet...

If you're new to Appium, or want a fuller description of what this is all about, please read our Introduction to Appium Concepts.

Requirements

Your environment needs to be setup for the particular mobile platforms that you want to run tests on. See below for particular platform requirements.

If you want to run Appium via an npm install, hack with or contribute to Appium, you will need node.js and npm 0.10 or greater (use n or brew install node to install Node.js. Make sure you have not installed Node or Appium with sudo, otherwise you'll run into problems). We recommend the latest stable version.

To verify that all of Appium's dependencies are met you can use appium-doctor. Run appium-doctor and supply the --ios or --android flags to verify that all of the dependencies are set up correctly. If running from source, you may have to use ./bin/appium-doctor.js or node bin/appium-doctor.js.

You also need to download the Appium client for your language so you can write tests. The Appium clients are simple extensions to the WebDriver clients. You can see the list of clients and links to download instructions at the Appium clients list.

iOS Requirements

Android Requirements

  • Android SDK API >= 17 (Additional features require 18/19)
  • Appium supports Android on OS X, Linux and Windows. Make sure you follow the directions for setting up your environment properly for testing on different OSes:

FirefoxOS Requirements

Quick Start

Kick up an Appium server, and then run a test written in your favorite WebDriver-compatible language! You can run an Appium server using node.js or using the application, see below.

Using Node.js

$ npm install -g appium
$ appium &

Using the App

Writing Tests for Appium

The main guide for getting started writing and running tests is the running tests doc, which includes explanations for iOS, Android, and Android older devices. If you're interested in testing on physical hardware, you might be interested in our real devices guide.

Essentially, we support a subset of the Selenium WebDriver JSON Wire Protocol, and extend it so that you can specify mobile-targeted desired capabilities to run your test through Appium.

You find elements by using a subset of WebDriver's element-finding strategies. See finding elements for detailed information. 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

This repository contains many examples of tests in a variety of different languages!

For the full list of Appium doc pages, visit this directory.

How It Works

Appium drives various native automation frameworks and provides an API based on Selenium's WebDriver JSON wire protocol.

Appium drives Apple's UIAutomation library for iOS support, which is based on Dan Cuellar's work on iOS Auto.

Android support uses the UiAutomator framework for newer platforms and Selendroid for older Android platforms.

FirefoxOS support leverages Marionette, an automation driver that is compatible with WebDriver and is used to automate Gecko-based platforms.

Contributing

Please take a look at our contribution documentation for instructions on how to build, test and run Appium from source.

Project Credits & Inspiration

Credits

Mailing List

Announcements and debates often take place on the Discussion Group, be sure to sign up!

Troubleshooting

We put together a troubleshooting guide. Please have a look here first if you run into any problems. It contains instructions for checking a lot of common errors and how to get in touch with the community if you're stumped.

Using Robots

Using Appium with Tapster and other robots is possible, check out the Appium Robots project!