Book Image

Mobile Test Automation with Appium

By : Nishant Verma
Book Image

Mobile Test Automation with Appium

By: Nishant Verma

Overview of this book

Appium is an open source test automation framework for mobile applications. It allows you to test all three types of mobile applications: native, hybrid, and mobile web. It allows you to run the automated tests on actual devices, emulators, and simulators. Today, when every mobile app is made on at least two platforms, iOS and Android, you need a tool that allows you to test across platforms. Having two different frameworks for the same app increases the cost of the product and time to maintain it as well. Appium helps save this cost. With mobile app growth exploding, mobile app automation is mainstream now. In this book, author Nishant Verma provides you with a firm grounding in the concepts of Appium while diving into how to set up appium & Cucumber-jvm test automation framework, implement page object design pattern, automate gestures, test execution on emulators and physical devices, and implement continuous integration with Jenkins. The mobile app we have referenced in this book is Quikr because of its relatively lower learning curve to understand the application. It's a local classifieds shopping app.
Table of Contents (20 chapters)
Title Page
Credits
About the Author
About the Reviewers
www.PacktPub.com
Customer Feedback
Preface
5
Understanding Appium Inspector to Find Locators
7
How to Automate Gestures
9
How to Run Appium Test on Devices and Emulators

Refactoring -1


Until now, we have been running the test via an IDE. When we started with the gradle file, it was majorly to pull in the dependencies needed for the project. Here's how the current version of the gradle file looks:

group 'com.test'
version '1.0-SNAPSHOT'

apply plugin: 'java'

//sourceCompatibility = 1.8

repositories {
    mavenCentral()
}

dependencies {
    testCompile group: 'junit', name: 'junit', version: '4.11'
    compile group: 'info.cukes', name: 'cucumber-java', 
    version: '1.2.5'
    compile group: 'io.appium', name: 'java-client', 
    version: '5.0.0-BETA6'
}

The next step is to create a task that will execute the cucumber features in a different feature file. A task represents an atomic piece of work for a build. Tasks generally belong to a project and the syntax to define a task is this:

task taskName (type: someType){
configuration
}

A task is made up of a sequence of actions; some typical actions can be added by calling doFirst() or doLast(). So, let's go...