Mobile application testing involves testing applications created for mobile devices to ensure proper functionality and compatibility. It includes testing installation/uninstallation, network connectivity, voice/SMS handling, user interface elements, battery usage, and compatibility with other device functions. The goal is to verify the application performs as intended under different conditions and does not disrupt normal device operation.

1. Mobile Application Testing
PPT
Prepared By
L. Eshwar
QA Engineer

2. What is Mobile Application Testing :
➢
It is somewhat similar to software testing but the testing will be
performed on a mobile device instead of performing on a system.
Difference between mobile testing and mobile
application testing:
Mobile Testing or Mobile Device Testing:
➢
➢
➢
Mobile Testing is testing of Mobile Handsets or devices.
Testing all the core like SMS ,Voice calls, connectivity(Blue tooth) ,
Battery(Charging),Signal receiving, Network are working correctly.
Testing is conducted on both hardware and software.
Mobile Application Testing:
➢
➢
Mobile Application Testing is the testing of mobile applications which we are making
as third party for the targeted mobile handset.
Some core feature of the mobile are tested just to see that your application has not
created any side effects on your device functionality.

3. Mobile Platforms
Android
 IOS(I phone)
 Symbian(Nokia)
 J2ME
 RIM(Blackberry)
 BREW
 Windows Mobile or Wince
 Bada(Samsung)
 Meego


4. Firmware

Firmware is a combination of software and hardware. Fixed
software programs that internally control various electronic devices
or individual hardware parts of these devices.

Computer chips that have data or programs recorded on them are
firmware. Firmwares are usually stored on ROM or OTP/EPROM,
while more complex firmwares occupy flash memory to allow for
updates.
Firmware Update:
 In order to improve the phone’s performance and to provide more
sophisticated features, firmwares are updated. Common reasons for
updating a firmware include fixing bugs or adding features to the
device.

5. Android

Android is an operating system for mobile devices developed by
Android. Later, the organization has been taken over by Google

The operating system is used in smart phones.

A smart phone is a device that lets you make telephone calls, but
also adds in features that, in the past, you would have found only on
a personal digital assistant or a computer--such as the ability to
send and receive e-mail and edit Office documents, for example.

6. Android Home Screen
44

7. Android Versions
Android 1.5 (Cupcake)
 Android 1.6 (Do nut)
 Android 2.1 (Eclair)
 Android 2.2 (Fro yo)
 Android 2.3 (Gingerbread)
 Android 3.X (Honeycomb)
 Android 4.0X (Ice Cream Sandwich)


8. IOS
IOS(I phone Operating System) is an operating system used in i
phones, i pads and i pods
List of I phone devices:
➢
➢
➢
➢
➢
I phone 2G
I phone 3G
I phone 3GS
I phone 4
I phone 4S

9. i pad
i Pad is primarily as a platform for audio-visual media including
books, periodicals, movies, music, games, apps and web content.
Its size and weight fall between those of contemporary smart
phones and laptop computers. The i Pad runs on i OS, the
same operating system used on Apple's i Pod Touch and i Phone
List of i pads:
➢


I pad
Ipad2
ipad3

10. i OS
List of i phone operating systems :
➢
ios1
 ios2
 ios3
 ios4
 ios5

11. Mobile Platforms
File Extensions
Android
.apk file
I phone
.ipa file
Symbian
.sis file
J2ME
.jad and .jar files
RIM
.alx and .cod files
Windows Mobile
.cab file
Bada
.jad and .jar files
BREW
.mif file

12. How to test a mobile application:
➢
Installation: Verify that application can be Installed Successfully.
Types of installation:
➢
➢
➢
➢
OTA(Over The Air)- Need GPRS Sim card and internet connection.
Wi fi
Data cable
Blue tooth
Un installation:
➢
Verify that application can be uninstalled successfully.
Network Testing:
➢
➢
➢
➢
Verify the behavior of application when there is Network problem
and user is performing operations for data call.
User should get proper error message like “Network error. Please
try after some time”
Verify that user is able to establish data call when Network is back
in action.
User should be able to establish data call when Network is back in
action.

13. Voice Call Handling:
Call Accept:
Call Rejection:
SMS Handling:
Unmapped Keys:
Verify that unmapped keys are not working on any screen of application.
External Volume control keys:

14. Application Logo:
Verify that application logo with Application Name is present in application manager and user can
select it.
Splash:
Verify that when user selects application logo in application manager splash is displayed.
Note that Splash do not remain for more than 3 seconds.
Low Memory:
Verify that application displays proper error message when device memory is low and exits gracefully
from the situation.
Clear Key:
Verify that clear key should navigate the user to previous screen.

15. End Key:
Verify that End Key should navigate the user to native OEM screen.
Visual Feedback:
Verify that there is visual feedback when response to any action takes more than 3 seconds.
Continual Keypad Entry:
Verify that continual key pad entry do not cause any problem.
Features to be checked while testing a touch screen device:
Touch functionality
Touch Response
Touch Area
Exit Application:
Verify that user is able to exit from application with every form of exit modes like Flip, Slider, End Key
or Exit option in application and from any point.
Charger Effect:

16. Low Battery:
Verify that when application is running and battery is low then proper message is displayed to the
user.
Removal of Battery:
Battery Consumption:
Verify that application does not consume battery excessively.
Application Start/ Restart:
1.
2.
3.
Find the application icon and select it 2.
“Press a button” on the device to launch the app. 3.Observe the application launch In the
timeline defined.
Application must not take more than 25s to start.
Application Side Effects:
Make sure that your application is not causing other applications of device to hamper.

17. External incoming communication – infrared:
Application should gracefully handle the condition when incoming communication is made via Infra
Red.
When the incoming communication enters the device the application must at least respect one of the
following: a) Go into pause state, after the user exits the communication, the application presents the
user with a continue option or is continued automatically from the point it was suspended at b) Give a
visual or audible notification The application must not crash or hung.
Bluetooth interrupt:
When a file transfer is taking place with bluetooth, the application must be paused and should be
resumed from the same point after the transfer is done.