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

Summary


In this chapter, we learned about the Page Object design pattern and how it can be used to give a structure to the code we have written. We also went through refactoring, understanding the design pattern and how it has significantly improved the code readability and makes the maintenance look easier. We learned about assertions and how they can be used. We also learned about where assertion belongs and the pros and cons of each approach. We discussed some framework design principles of avoiding the dependent test designs and the importance of hooks, such as @Before and @After, provided by cucumber.

Now we have a decent framework in structure and the tests are a little mature with the design pattern in place. The next step is to be able to run the test on different targets, such as an emulator and an actual device, understand the hassles around it, and solve them.