Today we are rattling excited to declare the general availability of Appium on Sauce! Appium is the open source cross-platform wandering automation program for native mobile, hybrid, and mobile web apps, and it runs on iOS (iPhone and iPad) and Android devices and emulators.Appiumtypify a huge step onward in the fight to make mobile automation a first-class citizen in peregrine development. We & # x27; ve been running our iOS-based private beta for Appium on Sauce for a while, and have made many improvements while supporting the development of the Appium open origin community. Since so, Android support has matured to the point where we are now offer it in our cloud alongside iPhone and iPad. Soon enough, we & # x27; ll be releasing the ability to run your Appium tests not only on our cloud of emulators and simulators, but also on real device (stay tune for more on that later!).

If you & # x27; re concerned in what Appium & # x27; s all about, say on. After lead thousands of lines of code to the open-source task and helping to breathe fire into what has become a very fighting community (see ourissue tracker, our discussion radical, or join us in # appium on freenode), it & # x27; s clear to us that Appium & # x27; s philosophy is obligate to a wide regalia of developers, examination engineers, and QA professionals. Appium & # x27; s philosophy can be express pretty succinctly in the form of four rule:

1. Test the same app you subject to the marketplace. (You shouldn & # x27; t have to recompile your app with a 3rd-party library to test it.)

2. Write your tests in any language, apply any framework. (You shouldn & # x27; t receive to hear a new language.)

3. Use a standard mechanization spec and API. (Don & # x27; t re-invent the automation poser wheel.)

   For autonomous testing across multiple user personas, check out SUSATest — it explores your app like 10 different real users.

4. Build a large and thriving open-source community effort. (Say no to vendorware and skunkworks.)

Based on the vast amount of zip we & # x27; ve been receiving from the growth of the open source community, I & # x27; d say these principles are withstanding examination. While Appium on its own is a leap forward in roving automation, allowing true cross-platform examination and scaling across the different dimensions of apps and devices (simulator vs. real devices, iOS vs. Android, native vs. loanblend), it is especially powerful when combined with. Sauce & # x27; s value has historically been most apparent in freeing web developers and testers from managing their own exam and reporting infrastructure. With Appium, this instant scalability is available to mobile-focused teams as well. Only on Sauce can you run your mobile tests across platforms in massive parallel, open up a world of possible for continuous integration and QA in general. Uninterrupted deployment for mobile apps, anyone? It & # x27; s potential, and with Appium on Sauce it can become the standard. If you & # x27; ve done, writing Appium tryout is as easygoing as writing the Selenium WebDriver examination you may be familiar with or may be already running on Sauce. You can write them in any speech (Python, Java, PHP, Ruby, Node.js, C #, Go, Haskell, etc ...) or test model (RSpec, PHPUnit, JUnit, Nose, Mocha, Vows, Cucumber, Capybara, etc ...). And of course, they arrive with the like great reporting (screenshots, videos, and require logarithm) as browser-based test sessions. I & # x27; ll leave you with an example test, lead a notes covering on Android (taken fromthis instance):

import os
from selenium importee webdriver

desired_caps = {}
desired_caps [& # x27; device & # x27;] = & # x27; Android & # x27;
desired_caps [& # x27; browserName & # x27;] = & # x27; & # x27;
desired_caps [& # x27; version & # x27;] = & # x27; 4.2 & # x27;
desired_caps [& # x27; app & # x27;] = & # x27; http: //appium.s3.amazonaws.com/NotesList.apk & # x27;
desired_caps [& # x27; app-package & # x27;] = & # x27; com.example.android.notepad & # x27;
desired_caps [& # x27; app-activity & # x27;] = & # x27; NotesList & # x27;

SAUCE_USERNAME = os.environ.get (& # x27; SAUCE_USERNAME & # x27;)
SAUCE_ACCESS_KEY = os.environ.get (& # x27; SAUCE_ACCESS_KEY & # x27;)

driver = webdriver.Remote (& # x27; http: // % s: % s @ ondemand.saucelabs.com:80/wd/hub & # x27; % (SAUCE_USERNAME, SAUCE_ACCESS_KEY), desired_caps)

el = driver.find_element_by_name (& quot; New note & quot;)
el.click ()

el = driver.find_element_by_tag_name (& quot; textfield & quot;)
el.send_keys (& quot; This is a new billet! & quot;)

el = driver.find_element_by_name (& quot; Save & quot;)
el.click ()

els = driver.find_elements_by_tag_name (& quot; text & quot;)
assert els [2] .text == & quot; This is a new note! & quot;
els [2] .click ()

driver.quit ()

You can likewise lead a look at aniPhone example test. Want to run Appium on Sauce right away? Simply and you & # x27; ll be good to go. If you & # x27; re already a Sauce user or client, you receive approach to Appium testing capability without any further steps. Once you & # x27; re ready to start writing your Appium tests, take a face at the to get started. And don & # x27; t forget to let us cognize how things are going for you in your seeking to entire mobile mechanization. Happy native app testing from all of us at Sauce!