Mobile App Interview Questions and Answers
Question - 41 : - What is the key difference between mobile device testing and mobile application testing?
Answer - 41 : -
Mobile device testing examines a device’s quality – by validating its hardware and software functions.This process aims to test features, i.e., screen, memory, camera, applications. It also consists of factory testing and certification testing.
Alternatively, mobile application testing means testing the mobile application on different mobile devices to ensure its consistency and functionality. After this process, you can measure the targeted application’s quality, whether it is well-suited for the device in terms of hardware, software, network connectivity, etc.
Question - 42 : - How many types of mobile applications? What are they?
Answer - 42 : -
There are three types of mobile applications:
Native Application
A native application is a software application built in a specific programming language for the particular device platform, iOS or Android. It can be easily installed into your devices and available in the application store (Google Play for Android and App Store for iOS), for example, WhatsApp or Facebook.
Web Application
A web application runs inside a mobile web browser, such as Chrome, Firefox, Opera, Safari using a mobile network or WIFI. For instance, some of the web applications are m.facebook.com, m.gmail.com, etc.
Hybrid Application
A hybrid application is a combination of a native app and a web app. Even though this type of application can be installed on a device just like a native app, it is a web app built with HTML, CSS, or JavaScript and runs in a webview.
Question - 43 : - What are the common challenges in mobile application testing faced by most testers?
Answer - 43 : -
- Executing test cases with various operating systems
- Testing application’s functionalities on a wide range of handsets
- Screen size fragmentation
- Testing applications on different mobile networks
- Different application types (native, hybrid or web app) require different ways to test
- The choice of the right mobile testing tool for QA team
Question - 44 : - What types of mobile testing should be included in the Android testing strategy?
Answer - 44 : -
A standard Android strategy can include these testing types: unit testing, system testing, integration testing, and operation testing subject to the features available of the tested mobile application. Other types of tests would also be performed if required, depending on the application’s features.
Question - 45 : - What is the strategy used to test a new mobile app? Which types of testing should be included?
Answer - 45 : -
A comprehensive test strategy should be planned based on specific guidelines to secure an effective performance of a new mobile application. Here are some of the essential points:
Selection of the devices – Understanding the market’s demand and the commonly used devices will be highly recommended before choosing the set of testing devices. (This choice could be dependent on the stakeholders or the app builders’ consideration)
Utilizing emulators – The use of emulators is useful, especially in the initial stages of development, since they allow quick checking of the app. It is a system that runs software from one environment to another environment without changing the software itself. It also duplicates the features and works on the real system.
Types of testing:
As for testing a new mobile application, several types of tests should be involved in order to ensure the app works as expected. Therefore, the strategy is all tied into these following types of testing:
- Functional testing
- System integration testing
- Installation and uninstallation of the application
- HTML control testing
- Performance testing
- Testing multiple mobile OS
- Cross-browser and cross-device testing
- Gateway testing
- Network and battery testing
Question - 46 : - List of the best practices for Android Testing
Answer - 46 : -
- Developers must prepare the test cases when they are writing the codes simultaneously.
- All of the test cases should be stored and well-documented for reusability.
- Apply continuous integration and execute tests once the code is changed
- Avoid using rooted devices and emulators to achieve the most reliable results
Question - 47 : - While planning to perform an end to end mobile testing, what are the primary criteria you have to consider?
Answer - 47 : -
In an end-to-end mobile testing process, QA teams test the entire application from beginning to end to ensure its flow behaves as expected. Throughout these steps, there are some of the many critical requirements to consider:
- Is the application successfully installed across various mobile models, gadgets, and operating systems?
- Does the application launch smoothly with or without a network?
- What are the orientations that the application supports and how do they work?
- Does the application perform well on different kinds of devices and network scenarios?
- How does the application respond when it is used? (i.e. response speed and time)
Question - 48 : - What are all major networks to be considered while performing application testing?
Answer - 48 : -
Performance application testing should cover all of the scenarios on different networks: 4G, 3G, 2G, and WIFI. Although 2G is a slower network, it is better to test on a slower network in order to track the application performance.
Question - 49 : - What is the best way to test different screen sizes of the devices?
Answer - 49 : -
Using emulators is the most effective way in case there are many different screen sizes of devices to test.
Question - 50 : - What are the common bugs that would often be found during the mobile testing process?
Answer - 50 : -
In general, some mobile testers classify the most frequently-found bugs into the four types:
- Critical bugs: The device’s operating system crashes when testing the application’s particular feature.
- Block bugs: Unresponsiveness of performance occurs even though the device status is still on.
- Major bugs: A specific feature of the application is unable to perform its functionality.
- Minor bugs: GUI bug is commonly the main case falling into a minor bug list.
Additionally, some other kinds of bugs are also found during the mobile application testing process, for example:
- Slow performance of an application
- Consumption more from the battery by an application
- Completely unresponsive behavior of an app