By-Anurag Khode,Copyright 2009-10
| 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. |
December 2, 2009 at 6:24 am
Great article. Keep posting more such articles. Can you post something on LMS testing
May 28, 2010 at 2:19 pm
Thanks SANTOSH!
February 26, 2010 at 5:09 am
Really good information about Mobile Testing.
May 28, 2010 at 2:19 pm
Thanks Spurthi!
February 28, 2010 at 3:49 am
It’s good article,Thanks for posting .
March 3, 2010 at 4:57 am
Thanks a lot!
March 15, 2010 at 7:30 am
Very very good article..It helped me a lot,Thanks for posting
March 15, 2010 at 12:34 pm
Thanks Nikila!
March 15, 2010 at 8:29 am
Great Anurag
Really a Good checklist covering important areas.
For iPhone apps testing visit
March 15, 2010 at 8:31 am
mobiletestersbay.blogspot.com
September 8, 2010 at 12:58 pm
great article . great thinking .it helps a lot .thanks
September 8, 2010 at 1:07 pm
Thanks prasankumar !
October 14, 2010 at 5:02 am
Thanx a Lot.
November 25, 2010 at 9:34 am
This post was really helpful for me to consolidate the idea of mobile testing. Nice work Anurag.
–thanks
md
December 4, 2010 at 6:27 am
Hi Anurag!
This looks perfect for me. Thanks for preparing the list of checklists while testing the “Mobile Applications”.
December 16, 2010 at 5:29 am
Nice Article…
Shall we add, ‘Replacing App’ when already same version or different version of App exist in our device.
January 13, 2011 at 5:27 pm
This is really ha helpful post
February 15, 2011 at 5:05 am
[...] Rogalsky A friend pointed out a good checklist of what to tes for mobile appst: http://mobileappstesting.com/200…Options • Insert a dynamic date hereView All 0 CommentsCannot add comment at this time.Add [...]
March 2, 2011 at 4:07 am
Great article,
Thanks.
April 25, 2011 at 9:40 pm
Excellent post.Thanks Anurag!
June 6, 2011 at 7:05 am
Good article and very informative too…
June 15, 2011 at 8:25 am
Thanks Ashwini !
August 25, 2011 at 7:22 pm
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.
August 28, 2011 at 4:50 pm
Thank you! I am happy that it helped you !
September 15, 2011 at 6:34 am
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
September 16, 2011 at 6:26 am
Thank you Anisha!
September 21, 2011 at 10:03 am
Thanks for sharing this post. I am tester for a mobile team and this document really helpful! thanks again.
September 23, 2011 at 6:05 am
Thanks and Most Welcome
November 11, 2011 at 6:10 am
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.
November 18, 2011 at 10:26 am
Thanks Vijayan!!
April 4, 2012 at 9:49 am
very nice article! keep up the good work! have been following your page since 3 days and find it very useful. go on!
April 5, 2012 at 1:58 am
Thanks meghna
May 14, 2012 at 5:34 am
Thanks Anurag for this information:) And i need UATP cases for android mobile..Where can i get it ?