iPhone Generic test cases

Replies to This Discussion

Permalink Reply by isiah schwartz on February 21, 2012 at 11:02pm

I dont work with iOS much, but I can give a few things to look for:

Make sure rotation doesnt break anything. Do this on every screen.

Consult the iphone offical spec guide to make sure everything matches.

check data over 3G vs Wi-fi

deactiveted location service to see if it effects anything.

Sorry, without more details this is pretty much all I can recommend.

• ▶ Reply

Permalink Reply by Kunal Tambe on February 22, 2012 at 12:48am

Hello All,

Sharing few high level scenarios specific to iPhone.

1. Orientation (Portrait/ Landscape)

2. Background/ foreground

3. Single/ Multi Touch

4. Swiping/ scrolling/ Pinch in

5. Online/Offline

6. UX

Thanks,

• ▶ Reply

Permalink Reply by sandeep kumar on February 22, 2012 at 10:00am

Thanks Guys... It helps a lot to me.

• ▶ Reply

Permalink Reply by ankit jain on February 22, 2012 at 10:40am

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.

 I think it's helpful for you......

Ankit

• ▶ Reply

Permalink Reply by sandeep kumar on February 22, 2012 at 10:50am

Thanks ankit..

• ▶ Reply

Permalink Reply by balika vitthal shinde on February 22, 2012 at 11:15am

thanx guys...

it helps a lot..

• ▶ Reply

Permalink Reply by Kunal Tambe on February 22, 2012 at 11:46am

Hello Ankit,

Thanks for pasting generic test cases for mobile Apps.

But Sandeep is looking for generic test cases based on iOS.

Any ways, thanks for the same.

Kunal Tambe
ankit jain said:

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.

 I think it's helpful for you......

Ankit

• ▶ Reply

Permalink Reply by Veera jeyamani on February 22, 2012 at 12:02pm

thanks ankit good show.... you have any test case for pen test.

• ▶ Reply

Permalink Reply by Arun Francis on February 23, 2012 at 11:47pm

From the above checklists u can prepare the TC'zz

1.) System Crash / Force Close

2.) Performance/memory testing

3.) Check with different networks -- WiFi and 3G,4G .also field and flight based(if needed).

4.) Check Installation -- Install the application being tested.

5.) Check Application start/stop behavior -- Start the application by selecting the icon or following the steps outlined in the submission statement

6.)Check if No disruption to voice calls -- With the application installed and running use a second phone to call the test device.

7.)Check if No disruption to text messages -- With the application installed and running, send a text message to the test device.

8.) Check for Auto-start behavior -- With the application running, find the settings for the application — either within the application itself or from the settings option on the device.

9.) Check for Multitasking -- No disruption to key device applications

10.) Check for navigations, tabs,page scrolling etc..

11.) Check for social networking options such as sharing ,posting and links etc..

12.) Memory testing -- check the memory by filling and emptying it ,then compare the application with it.

13.)  Check if any payment gateway occurs like paypal,chargify etc...

14.)  Check uninstall of apps -- The application must be uninstalled without error. 

Also hav a look @ this: 

--> Perform multitasking or multiprocessing  in mobile application and compare the performance b4 and after this process.

 $ Fill the memory and test whether the application s performing well or not.In some cases if the memory is full then the application works slowly and zero performance exists.

$ Test the load time in application inner and outer areas.., means that interior page loading time (articles,images).

$ Test the page navigations simultaneously.

$Test in different devices for the best performance.

-Nexus One 2.2+

- Moto Droid X (2.1)

- Samsung Galaxy S (2.1)

- Nexus One (2.1)

- HTC Desire (2.1)

- SE Xperia X10i (1.6)

- Moto Droid (2.0)

- HTC Magic (1.5)

 IPhone -- Check for 2g,3g and 4g

$ Test whether Forceclose/sytem crash occurs during the page loading and navigations.In these the application faces lot of Force closes and performance becomes null.

$ Test simultaneously the menus present  in the same page and check the performance.

$ Perform negative test cases for best performance of application ....via both functionality and design
So based on these things u can elaborate the test cases for the Iphone and android appications.

• ▶ Reply

▶ Reply to Discussion