Testing Checklist for Mobile Applications

49
7065

By-Anurag Khode,Copyright 2012-13

No. Module Sub-Module Test Case Description Expected Result
1 Installation
Verify that application can be Installed Successfully. Application should be able to install successfully.
2 Uninstallation
Verify that application can be uninstalled successfully. User should be able to uninstall the application successfully.
3 Network Test Cases
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”
4

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.
5 Voice Call Handling Call Accept Verify that user can accept Voice call at the time when application is running and can resume back in application from the same point. User should be able to accept Voice call at the time when application is running and can resume back in application from the same point.
6
Call Rejection Verify that user can reject the Voice call at the time when application is running and can resume back in application from the same point. User should be able to reject the Voice call at the time when application is running and can resume back in application from the same point.
7
Call Establish Verify that user can establish a Voice call in case when application data call is running in background. User should be able to establish a Voice call in case when application data call is running in background.
8 SMS Handling
Verify that user can get SMS alert when application is running. User should be able to get SMS alert when application is running.
9

Verify that user can resume back from the same point after reading the SMS. User should be able to resume back from the same point after reading the SMS.
10 Unmapped keys
Verify that unmapped keys are not working on any screen of application. Unmapped keys should not work on any screen of application.
11 Application Logo
Verify that application logo with Application Name is present in application manager and user can select it. Application logo with Application name should be present in application manager and user can select it.
12 Splash
Verify that when user selects application logo in application manager splash is displayed. When user selects application logo in application manager splash should be displayed.
13

Note that Splash do not remain for fore than 3 seconds. Splash should not remain for fore than 3 seconds.
14 Low Memory
Verify that application displays proper error message when device memory is low and exits gracefully from the situation. Application should display proper error message when device memory is low and exits gracefully from the situation.
15 Clear Key
Verify that clear key should navigate the user to previous screen. Clear key should navigate the user to previous screen.
16 End Key
Verify that End Key should navigate the user to native OEM screen. End Key should navigate the user to native OEM screen.
17 Visual Feedback
Verify that there is visual feedback when response to any action takes more than 3 seconds. There should be visual feedback given when response time for any action is more than 3 second.
18 Continual Keypad Entry
Verify that continual key pad entry do not cause any problem. Continual key pad entry should not cause any problem in application.
19 Exit Application
Verify that user is able to exit from application with every form of exit modes like Flap,Slider,End Key or Exit option in application and from any point. User should be able to exit with every form of exit modes like Flap,Slider,End Key or Exit option in application and from any point.
20 Charger Effect
Verify that when application is running then inserting and removing charger do not cause any problem and proper message is displayed when charger is inserted in device. When application is running then inserting and removing charger should not cause any problem and proper message should be displayed when charger is inserted in device.
21 Low Battery
Verify that when application is running and battery is low then proper message is displayed to the user. When application is running and battery is low then proper message is displayed to the user telling user that battery is low.
22 Removal of Battery
Verify that removal of battery at the time of application data call is going on do not cause interruption and data call is completed after battery is inserted back in the device. Removal of battery at the time of application data call is going on should not cause interruption and data call should be completed after battery is inserted back in the device.
23 Battery Consumption
Verify that application does not consume battery excessively. The application should not consume battery excessively.
24 Application Start/ Restart
1. 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.
25 Application Side Effects
Make sure that your application is not causing other applications of device to hamper. Installed application should not cause other applications of device to hamper.
26 External incoming communication – infrared
Application should gracefully handle the condition when incoming communication is made via Infra Red [Send a file using Infrared (if applicable) to the device application presents the user] 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.

49 COMMENTS

  1. This post was really helpful for me to consolidate the idea of mobile testing. Nice work Anurag.
    –thanks
    md

  2. Hi Anurag!

    This looks perfect for me. Thanks for preparing the list of checklists while testing the “Mobile Applications”.

  3. Nice Article…
    Shall we add, ‘Replacing App’ when already same version or different version of App exist in our device.

  4. Awesome checklist, I am about to start testing my first mobile app and had already written some tests before I found your checklist, there were some things that I had missed, thank you.

  5. Excellent article, i was about to start my new project and being a fresher was trying to prepare which all are the points i need to cover, your checklist helped a lot.. Great help for freshers :)

  6. Thanks for sharing this post. I am tester for a mobile team and this document really helpful! thanks again.

  7. […] 2. Testing Checklist for Mobile Applications […]

  8. Hi Anurag,

    Excellent article!!.

    I would like to add one more Test Scenario/module here.

    Scenario: Running Multiple Instances

    T/C Desc : 1. Run the application, do some data call without closing, go to main screen.
    2.Open one more instance of the application

    Expected Result : Should open the previous session. Should not allow to run multiple instances.

    Note : Running multi instances may vary based on the application requirement.

  9. very nice article! keep up the good work! have been following your page since 3 days and find it very useful. go on!

  10. Excellent Article, I am planning use this content as part of my help document that I preparing for my company.

    I will put this article link in the refrences section.

    Thanks,
    Siva

  11. Hi Anurag,
    Can you please tell me how Mobile Netwrok Testing Done . Are there any tools required to test the Mobile Network

    • Hi Razak,

      You can use Charles Proxy to throttle network. This would help you create the bandwidth of different networks.It is advised to use real networks to perform network testing.

      Test your app on :

      Wi-fI
      2g
      3g
      4g

      Test while switching network. I couldn’t find the good tool to create the scenario when a network move from 2g to 3g and vice versa. We use to do field testing in this case sometimes where we test app while moving from one place to other.

      For simulating networks like Verizon, Sprint etc in US, you can use a network simulator tool Anritsu, which create same network as these network providers. This tool is however very costly.

  12. Hi Anurag,
    Really a Good checklist covering important areas.I suggest adding a module “push notification” because that’s a very important feature in mobile applications.

Leave a Reply