Top 25 Popular Appium Interview Questions And Answers

This tutorial provides frequently asked Appium interview questions and answers with explanations to help you prepare for the Appium interview.

Appium is an open-source mobile automation UI testing framework to test native, mobile, and hybrid (a combination of native and mobile) web applications. You can test your mobile applications on iOS and Android platforms or using an emulator or simulator. It uses the WebDriver protocol for iOS, Android, Mac, and Windows applications.

To run Appium on your client machine, Appium server and client bindings for a preferred programming language must be installed. The programming languages preferred by client binding are Java, JavaScript with Node.js, PHP, Python, Ruby, and Robot Framework.

Appium has a wrapper or framework that translates Selenium WebDriver commands into iOS or Android commands based on device type.

Expert Quiz on Appium Interview Questions

A tailored quiz on Appium Interview Questions for both freshers and experienced professionals. This quiz covers all essential questions on Appium concepts, fundamentals, and architecture, scripting, and advanced topics to sharpen your Appium skills.

Understanding Appium

Appium is a mobile test framework that allows test tools, frameworks, or test practices of our preference; it does not need an SDK or re-compiling native applications to test.

It is built on the Selenium WebDriver API and language-specific client libraries, making it a test framework that helps to automate mobile applications. You can use the programming language and test framework of your choice to develop test automation scripts that are accessible with back-end APIs and DBs.

Appium Testing Interview Questions

Q #1) Describe various types of mobile applications

Answer: Mobile applications are of the following three types:

• Native Applications: Applications that are created with the help of iOS and Android SDK are Native Applications. Native applications developed for Android will not work on iOS phones and will not be available on iOS App Stores. Native applications designed and optimized for specific platforms offer the best performance, UI/UX suitable to run on that platform, Google Play Store support, offline mode, consistent look and feel, security and data protection, and fewer bugs during development. Some examples of Native applications are the mobile version of WhatsApp, Amazon Prime, LinkedIn, etc.
• Mobile Web Applications are actual websites developed in HTML5, accessible by browser, and can be accessed offline because of the browser cache. Some examples of mobile web applications are newspapers as ePaper, Google applications like Drive, Gmail, Docs, Sheets, Forms, and Photos, etc.
• Hybrid Applications are a mix of native and web applications. Similar to native applications, they are found on mobile app stores and offer comparable functionalities. Web applications need web browsers for their rendering. Online e-commerce platforms and Netflix serve as prime examples of hybrid applications.

Native, Mobile, and Hybrid Mobile Application:

Q #2) What is the difference between iOS and Android?

Answer: Both iOS and Android are used as operating systems for mobile devices. I have listed their differences below:

Q #3) What hardware and software are the prerequisites for using Appium?

Answer: The list of software required before installing Appium is as follows:

Hardware requirement:

• 8 GB RAM Memory
• Windows 10
• .NET Framework 3.5 or higher.

Software requirement:

• Java Development Kit (JDK) – It should have at least JDK version 8 or higher.
• Android SDK version 22 has separate platforms and build tools, suitable for Appium.
• Node.js is needed for a non-blocking event-based server to handle multiple WebDriver sessions for iOS and Android platforms.
• Microsoft WebDriver – also known as WinAppDriver, Appium-compatible WebDriver server – Need Windows 10 or above.
• PDANet+ – It is a free application that converts an Android or iOS mobile into a modem and enables tethering.
• Appium – Client libraries and Desktop applications of Appium are mandatory
• GenyMotion – It is required to run Appium tests in multiple virtual Android devices in parallel.
• ADT Plugin to access Android SDK within Eclipse.
• Java Client Drivers are also known as language binding for creating tests in multiple programming languages.
• Appium Client Libraries support Appium extensions to the WebDriver protocol by the Appium Server.

Q #4) List the advantages of using Appium.

Answer: It offers the following advantages:

• It is open-source, supports both iOS and Android
• We can design an automation script using the same API for Android and iOS.
• Supports multiple languages like Java, Node.js, Ruby, Python, and Robot framework and is cross-platform.
• Can be integrated with continuous integration tools.
• Issues like synchronization are avoided.
• Uses the HTTP protocol and is based on Selenium

Q #5) List the limitations of using Appium

Answer: The following are some limitations:

• The time needed and configuration for Appium setup are complex
• It can run a single iOS device at a time.
• There is no support for automation for Android 4.1 or lower.
• There is no support for Windows for the Appium inspector.
• Limited support for testing hybrid applications.
• You cannot test the switching action of native to the web or vice versa.

Q #6) Explain the working of Appium

Answer: The working of Appium is explained below:

1. Appium server developed using Node.js implements Selenium WebDriver.
2. The connection request is sent by the WebDriver script to the Appium server via the JSON Wire protocol.
3. Automation session and desired capabilities are set
   • With Android, the request is sent to UIAutomator, UIAutomator communicates with bootstrap.jar running on an Android mobile device or emulator to perform operations.
   • Whereas for iOS, UIAutomation receives requests. UIAutomation communicates with bootstrap.js running on iOS mobile devices or emulators to perform operations.
4. After execution of the request, the message is sent back to the Appium server. Server logs capture the results of execution.

Working of Appium:

Q #7) Describe the JSON wire protocol used in Appium.

Answer: JSON wire protocol uses a RESTful API to communicate between the Appium client and server, controls the behavior of mobile phones, in addition to setting the communication stream.

Q #8) List locators used in Appium

Answer: The list of locators supported is as follows:

• ID
• Class Name
• XPath
• Accessibility ID
• Android UI Automator
• iOS UI Automation
• Android View Tag using Appium Espresso

Q #9) List the differences between Selenium WebDriver and Appium WebDriver

Answer: Selenium and Appium both use

• JSON wire protocol
• Methods like
  • sendKeys(),
  • findByClassName(),
  • findByElementId(),
  • findByXPath()

There is a difference between Selenium WebDriver and Appium WebDriver as follows.

Q #10) What is Selendroid?

Answer: Selendroid is a mobile automation tool for Android-based applications that uses the Selenium WebDriver client API. It uses an inspector for monitoring the current UI status.

Q #11) List the activities possible with the real device but not with the emulator.

Answer: The list of functionalities that are not possible with an emulator is as follows:

• Make or receive calls, send or receive SMS,
• Battery issues, GPS tracking, gesture recognition, touch screen functionality
• Changing color over the screen, widgets, and accessing the file
• Selecting icons to access the application with the help of fingers (touch screen),
• Typing the text and moving the mouse on a real mobile screen will differ from that of an emulator.
• Performance tracking of the installed mobile application, etc.

Q #12) What is Espresso?

Answer: Espresso is a test automation framework for Android. It is a UI automation framework suitable for black-box testing that uses JUnit4 annotations. Developers write Espresso tests in Java and Kotlin. Appium uses Espresso with Android View Tag.

Advanced Questions for Appium Interview

Q #13) What is XCUITest?

Answer: XCUITest is an automation framework for iOS. This framework is used to test only native mobile applications that are built using Swift or Objective-C. XUITest cannot write tests for multiple platforms. Appium uses the XCUITest driver for automating iOS applications.

Q #14) List some common exceptions in Appium observed during test automation.

Answer: The following are some commonly encountered exceptions in Appium during script execution:

• SessionNotFoundException: On disconnection of Appium connection or Session not established, display this exception
• ElementNotFoundException: When Appium does not find the element it is looking for, this exception is displayed
• WebDriverException: When Driver does not exist, this exception is displayed
• NoSuchContextException: is thrown when the context target that is to be switched to does not exist.

Q #15) List the differences between the working of Appium on Android and iOS.

Answer: Appium executes tests differently on Android and iOS-based mobile devices.

• Appium uses the UIAutomator framework for automation when testing Android-based mobile applications.
• Appium on the iOS mobile device uses Apple’s XCUI Test API to interact with UI elements to test their functionality.
• UI Automator connects with bootstrap.jar being executed in a simulator/emulator or real device that performs client operations.
• XCUI Test in case of iOS mobiles communicates with bootstrap.jar
• Bootstrap.jar acts as a TCP server that accepts test commands to test the functionality of Android-based mobile devices that use UI Automator.
• Bootstrap.jar acts on the iOS mobile application being tested, and Appium Client sends a message with log details of commands executed.

Q #16) List the essentials you need to write the Appium test?

Answer: The essential things required are:

• Driver – Set of APIs helps write tests, and commands are sent to the HTTP Server for processing.
• Session – Session instances should be created during the execution of automation testing and closed after execution.
• Capabilities – Set up of Chrome Driver path to execute tests in the Chrome browser and defining params like PlatformName, PlatformVersion, and DeviceName,
• Commands – Appium requires commands that are action words that perform test steps.

Q #17) Describe desired capabilities in Appium

Answer: Desired capabilities are keys and values inside JSON objects sent by the Appium client to the server to perform all the actions required to test the functionality.

Q #18) What are the properties present in key-value pairs in desired capabilities?

Answer: A few of the properties are explained that are present in keys and values form in desired capabilities as below:

• automationName: Provides the name of the automation engine that will be used. Appium is used by default, and Espresso, UIAutomator1 & 2 for Android, and XCUITest for iOS.
• platformName: Name of mobile OS platform being used, for example, iOS, Android, or FirefoxOS
• platformVersion: Version of mobile OS, such as 7.1, 4.4, etc.
• deviceName: Mobile device or emulator type – iPhone Simulator, Android Emulator, etc.

Q #19) List design considerations in Appium

Answer: The following are some points taken into consideration in Appium Design:

• Node.js should be installed already on the system, as Appium Server is actually an HTTP server designed using Node.js that drives iOS and Android sessions with the help of WebDriver JSON wire protocol.
• Appium server installed on the system acts as a REST API.
• Appium server receives connection and command requests, whereas the command executes on iOS/Android devices.
• Appium server sends HTTP responses to interact with the user interface using the mobile test automation framework.
• There are various frameworks for
  • iOS mobile devices
  • Google UI Automator for Android API level 16 or higher
  • Selendroid for Android API level 15 or higher

Q #20) Explain implicit and explicit wait in Appium

Answer: Appium Web Driver checks the web element or certain conditions with the help of locators.

Various waits are applied during the execution of the automation script and are explained below:

Implicit Wait: WebDriver will make the automation script wait for a certain period in search of a web element. After this time, if the element does not display, the error “No such Element found Exception” will be thrown.

Syntax:

driver. manage(). timeouts(). implicitlyWait (TimeOut, TimeUnit.SECONDS);

Explicit Wait: The Web Driver will wait for a certain condition OR will throw “ElementNotVisibleException” exception after the maximum time for waiting exceeds.

Some conditions for explicit wait are:

• alertIsPresent(),
• elementToBeClickable()
• presenceOfAllElementsLocatedBy()
• textToBePresentInElement()
• visibilityOf()

Syntax:

WebDriverWait wait = new WebDriverWait(driver, 15); 
wait.until(ExpectedConditions.textToBePresentInElement(By.xpath("xpath"), "Text"));

Q #21) List common pitfalls you should avoid while writing Appium tests.

Answer: While writing Appium tests, the following points should be taken into consideration:

• Avoid excessive use of XPath as a locator.
• Use the accessibility ID locators for both iOS and Android mobile device testing.
• Querying for the visibility of elements should only be restricted to important elements.

Q #22) What is the purpose of Appium Inspector?

Answer: Appium Inspector is a utility provided by the Appium automation framework that helps to load mobile applications and locate elements.

Q #23) Describe ways to debug Appium tests.

Answer: The following are some ways we can do this:

• You can trace any error that occurred during mobile tests from the logs the Appium server generated.
• Test scripts created can be debugged with the help of the programming language used in writing these tests.

Q #24) How can we retrieve the test status of the Appium test execution?

Answer: There are various ways to display the test status:

• Integrating TestNG with Appium
• ExtentReports that give test status reports in the dashboard
• REST API of BrowserStack App Automate for .apk (Android app) or .ipa (iOS app).
• Built-in reporting tools like Maven and Allure

Q #25) What is Calabash?

Answer: Calabash is a mobile test automation framework for testing mobile devices based on iOS and Android platforms. Tests are written using Cucumber, Gherkin, and Ruby code.

Conclusion

Appium is an industry-standard mobile automation framework to test the functionality of native, hybrid, and web-based applications on iOS and Android mobile devices.

Various questions, such as configuration needed before installation, the working of Appium, pros and cons of its use, internals, and design considerations, have been answered.

Mobile testing is testing mobile applications on iOS and Android devices, simulators, and emulators for usability, functionality, and consistency. Appium is used as a mobile automation test framework for Android and iOS mobile applications. Espresso is for Android-based mobile testing, whereas XCUITest is for iOS-based mobile testing.

For more Appium-related guides, you can explore our range of tutorials below:

• Appium Tutorial for Beginners for Mobile App Testing
• Introduction to Appium Studio: Key Benefits and Features
• Download, Install And Setup Appium For Windows
• Introduction To Appium: What Is Appium And Its Architecture
• Appium Studio Tutorial for Mobile Automation – Software Testing Help