Wednesday, 12 February 2014

Basic Mobile testing checklist



Instal­la­tion :
            Ver­ify that appli­ca­tion can be Installed Successfully. 

Unin­stal­la­tion : 
User should be able to unin­stall the appli­ca­tion successfully.

Appli­ca­tion Logo :
            Appli­ca­tion logo with Appli­ca­tion name should be present in appli­ca­tion man­ager and user can select it. 

Splash Screen:
            When user selects appli­ca­tion logo in appli­ca­tion man­ager splash should be displayed. Note that Splash do not remain for more than 7 seconds. 

navigation Testing :
Check the navigation of the application. User should not get stuck anywhere within the application. 

UI Testing: 

Check the Usability scenarios as follows 

·         Text getting overlapped.
·         Typo mistakes.
·         Alignment issues on border line.
·         Junk Char displayed on the article.

Net­work Testing : 
            User Invoking the Application during no n/w connection
·         App should not get crash.
·         Should get proper error mes­sage like “No Net­work Connection. Please try after some time”. 

             Invoking the Application After the n/w connection
·         App should load and display the latest content instead of stale content. 

Voice Call Handling :   
·         Call Accept :  User should able to accept voice call at the time when the application is running and resume back in application from the same point. 

·         Call Reject : User should able to reject voice call at the time when the application is running and resume back in application from the same point.

·         SMS Han­dling  : User should able to get SMS alert when the application is running .

Low Mem­ory  :
Appli­ca­tion dis­plays proper error mes­sage when device mem­ory is low and exits grace­fully from the situation. 

Scenarios have to check how the application is performing on various scenarios such as Removal of  Battery , While charging , Low Battery.

Data connectivity : Application should work perfectly on the connections such as Wifi / 2 G network / 3G Network . it should not get Crash.

Orientation./Portrait testing : App should load and work fine on both landscape & Portrait format. also check the user can able to upload image on Landscape mode & check the app on Portrait mode after successful uploading and Vice versa...

XML testing : by changing the content on the XML and check whether App is working or not.
Web service testing :  by removing the content on the XML and check whether App is working or not.

Sharing Functionality –  check whether the user try to post comments, share the article through Mail, SMS , FB/Twitter account.  Check the article short URL is displaying  or not after message is received.

Memory Related Testing for Mobile Application
 1. Fill up the phone memory with other files and data, then try to install the APP on the phone.
Expected result: The APP should not get installed on the phone and the user should be shown a native warning from the phone OS.
2. Fill up the memory with files and data and leave exactly the same amount of memory required for the installation of the APP.
Expected result: APP should get installed on the phone, but as you launch the APP the phone should refuse as it doesn't have even 1 KB of extra space that the APP might require to cache some data.
3. Run the App in low memory: Leave only a small amount (5-7 KB) of space for the app to run. While you are in the app and continuously making server calls this memory will also get filled up.
Expected result: The app should give a warning stating low memory

2 comments:

  1. Thanks for sharing this article .

    ReplyDelete
  2. Very good work..can share test cases for book my show application for android mobile

    ReplyDelete