[UPDATE- November 2019] You can find the newest Get Started with Appium white papers here: Get Started with Appium- Java and Get Started with Appium- Ruby
This is the seventh post in a series called Appium Bootcamp by noted Selenium expert Dave Haeffner.
Dave recently immersed himself in the open source Appium project and collaborated with leading Appium contributor Matthew Edwards to bring us this material. Appium Bootcamp is for those who are brand new to mobile test automation with Appium. No familiarity with Selenium is required, although it may be useful. This is the seventh of eight posts; two new posts will be released each week.
To make our tests as useful as possible, we'll want to automate when they get run. To do that, we'll use a Continuous Integration (CI) Server.
A Continous Integration server (a.k.a. CI) is responsible for merging code that is actively being developed into a central place (e.g., "trunk" or "master") frequently (e.g., several times a day, or on every code commit) to find issues early so they can be addressed quickly -- all for the sake of releasing working software in a timely fashion.
With CI, we can automate our test runs so they can happen as part of the development workflow. The lion's share of tests that are typically run on a CI Server are unit (and potentially integration) tests. But we can very easily add in our automated mobile tests.
There are numerous CI Servers available for use today. Let's pick one and step through an example.
Jenkins is a fully functional, widely adopted, and open-source CI server. It's a great candidate for us to step through.
Let's start by setting it up on the same machine as our Appium Server. Keep in mind that this isn't the "proper" way to go about this -- it's merely beneficial for this example. To do it right, the Jenkins server (e.g., master node) would live on a machine of its own.
A simple way to get started is to grab the latest Jenkins war file. You can grab it from the Jenkins homepage, or from this direct download link.
Once downloaded, launch it from your terminal.
java -jar /path/to/jenkins.war
You will now be able to use Jenkins by visiting [http://localhost:8080/](http://localhost:8080/) in your browser.
After loading Jenkins in the browser, we'll create a Job and configure it to run our Appium tests. Let's start with the Android tests first.
Click New Item in the top-left corner
Type a name into the Item name input field (e.g., Appium Android)
Select Build a free-style software project
This will load a configuration screen for the Jenkins Job.
Scroll down until you reach the Build section (near the bottom of the page)
Click Add build step
Select Execute shell
Input the following into the Command input box
cd /path/to/your/appium/test/code bundle update rake android
In this set of commands we are telling Jenkins to change directories to our test code, make sure we have the necessary libraries, and then launch the Android tests.
Save at the bottom of the page, make sure your Appium Server is running (if not, load up the Appium GUI and click
Launch), and click
Build Now on the left-hand side of the Jenkins Job screen.
Once it's running, you can click on the job under Build History, and then click Console Output (from the left-hand panel). In it, you should see something similar to this:
1Started by user anonymous2Building in workspace /Users/tourdedave/.jenkins/jobs/Appium Android/workspace3[workspace] $ /bin/sh -xe /var/folders/yt/h7v9k6px7jl68q81c9sqrd9h0000gn/T/hudson6140596697737249507.sh4+ cd /Users/tourdedave/Dropbox/_dev/appium/appium-getting-started/code-examples/7/15+ bundle update6Fetching gem metadata from https://rubygems.org/...........7Fetching additional metadata from https://rubygems.org/..8Resolving dependencies...9Using rake 10.3.210Using awesome_print 1.2.011Using json 1.8.112Using mini_portile 0.6.013Using nokogiri 220.127.116.11Using ffi 1.9.315Using childprocess 0.5.316Using multi_json 1.10.117Using rubyzip 1.1.618Using websocket 1.0.719Using selenium-webdriver 2.42.020Using blankslate 18.104.22.1681Using parslet 1.5.022Using toml 0.1.123Using appium_lib 4.0.024Using bond 0.5.125Using coderay 1.1.026Using method_source 0.8.227Using slop 3.6.028Using pry 0.9.12.629Using numerizer 0.1.130Using chronic_duration 0.10.531Using spec 5.3.432Using appium_console 1.0.133Using diff-lcs 1.2.534Using mime-types 1.25.135Using rdoc 4.1.136Using rest-client 1.6.837Using rspec-support 3.0.338Using rspec-core 3.0.339Using rspec-expectations 3.0.340Using rspec-mocks 3.0.341Using rspec 3.0.042Using sauce_whisk 0.0.1343Using bundler 1.6.244Your bundle is updated!45+ rake andorid46.4748Finished in 38.39 seconds (files took 1.52 seconds to load)491 example, 0 failures50Finished: SUCCESS
We now have a working job in Jenkins. But we're not there yet. While the job was runnning you should have seen the Android Emulator open, load the test app, and perform the test actions. Unfortunately, after the job completed, the emulator didn't close.
Closing the Android Emulator is something that Appium doesn't handle, so we'll need to account for this in our Jenkins build configuration. Otherwise, we won't leave things in a clean state for future test runs.
The simplest way to close the emulator is by issuing a
kill command against the name of the process (ensuring that the command always returns
true). That way we cover our bases in case there is more than one emulator process running or if we try to kill a process that doesn't exist. So let's go ahead and add the
kill command to our existing commands under the
Build section of our job. For good measure, let's add it before and after our test execution commands.
To get back to the job configuration screen, click
Configure from the main job screen.
killall -9 emulator64-x86 || true cd /path/to/your/appium/test/code bundle update rake android killall -9 emulator64-x86 || true
Now let's save the job and build it again. The job will run just like before, but now the emulator will close after the test run completes.
Now let's create a second job to run our tests against iOS.
To save a step, let's create a copy of our existing job and modify the build commands as needed.
Click the Jenkins logo at the top of the screen (it will take you to the main page)
New Item in the top-left corner
Type a name into the
Item name input field (e.g.,
Copy existing Item
Start to type in the name of the other job in the
Copy from input field (e.g.,
Select the job from the drop-down as it appears
This will take us to a configuration screen for the new (copied) job. Let's scroll down to the
Build section and modify the
Command input field under
killall -9 "iPhone Simulator" &> /dev/null || true killall -9 instruments &> /dev/null || true cd /path/to/your/appium/test/code bundle update rake ios killall -9 "iPhone Simulator" &> /dev/null || true killall -9 instruments &> /dev/null || true
Similar to the Android job, we're using
kill to end a process (in this case two processes) and making sure the command returns
true if it doesn't exist. This protects us in the event that the test suite doesn't complete as planned (leaving a simulator around) or if the simulator doesn't close instruments cleanly (which can happen).
If we save this and build it, then we will see the iPhone Simulator load, launch the app, run the tests, and then close the simulator.
We've covered running things locally on the CI server, now let's create a job to run our tests on Sauce.
Let's create another copy of the
Appium Android job and modify the build commands.
Since we're not going to be running locally, we can remove the
kill line. We'll then specify our Sauce credentials (through environment variables) and update the
rake command to specify
'sauce' as a location. When we're done, our
Command window should look like this:
export SAUCE_USERNAME=your-username export SAUCE_ACCESS_KEY=your-access-key cd /path/to/your/appium/test/code bundle update rake android['sauce']
If we save this and build it, our tests will now run on Sauce Labs. And you can view them as they happen on your Sauce Labs Account Page.
An iOS job would be identical to this, except for the job name (e.g.,
Appium iOS Sauce) and the
rake incantation (which would be
Now that we have our Appium tests wired up for automatic execution, we're now able to configure them to run based on various triggers (e.g., other CI jobs, a schedule, etc.). Find what works for you and your development team's workflow, and make it happen.
About Dave Haeffner: Dave is a recent Appium convert and the author of Elemental Selenium (a free, once weekly Selenium tip newsletter that is read by thousands of testing professionals) as well as The Selenium Guidebook (a step-by-step guide on how to use Selenium Successfully). He is also the creator and maintainer of ChemistryKit (an open-source Selenium framework). He has helped numerous companies successfully implement automated acceptance testing; including The Motley Fool, ManTech International, Sittercity, and Animoto. He is a founder and co-organizer of the Selenium Hangout and has spoken at numerous conferences and meetups about acceptance testing.
Follow Dave on Twitter - @tourdedave
Continue the reading the other chapters: