Smoke Test Checklist for Mobile Application Testing

January 11, 2017 | Author: Anand | Category: N/A
Share Embed Donate


Short Description

Download Smoke Test Checklist for Mobile Application Testing...

Description

Basic Smoke Test Scenarios for Mobile Application Testing

No.

Module

1

Installation

2

Uninstallation

3

Network Test Cases

Sub-Module

4

5

Voice Call Handling

Call Accept

6

Call Rejection

7

Call Establish

8

SMS Handling

9

10

Unmapped keys

11

Application Logo

12

Splash

13 14

Low Memory

15

Clear Key

16

End Key

17

Visual Feedback

18

Continual Keypad Entry

19

Exit Application

20

Charger Effect

21

Low Battery

22

Removal of Battery

23

Battery Consumption

24

Application Start/ Restart

25

Application Side Effects

26

External incoming

27

communication – infrared External incoming

communication – infrared

28

External incoming

29

communication – infrared External incoming

communication – infrared

Test Case Description

Expected Result

Verify that application can be Installed Successfully. Verify that application can be uninstalled successfully. Verify the behavior of application

Application should be able to install successfully. User should be able to uninstall the application successfully. User should get proper error

when there is Network problem and user is performing operations for data call. Verify that user is able to establish data call when Network is back in action. Verify that user can accept Voice

message like “Network error. Please try after some time” User should be able to establish data call when Network is back in action. User should be able to accept Voice

call at the time when application is call at the time when application is running and can resume back in

running and can resume back in

application from the same point. 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. Verify that user can establish a Voice call in case when application data call is running in background. Verify that user can get SMS alert

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. User should be able to establish a

when application is running. Verify that user can resume back from the same point after reading the SMS. Verify that unmapped keys are not working on any screen of application. Verify that application logo with Application Name is present in application manager and user can select it. Verify that when user selects application logo in application manager splash is displayed.

when application is running. User should be able to resume back from the same point after reading the SMS. Unmapped keys should not work on

Voice call in case when application data call is running in background. User should be able to get SMS alert

any screen of application. Application logo with Application name should be present in application manager and user can select it. When user selects application logo in application manager splash should be displayed.

Note that Splash do not remain for fore than 3 seconds. Verify that application displays proper error message when device memory is low and exits gracefully from the situation. Verify that clear key should navigate the user to previous screen. Verify that End Key should navigate the user to native OEM screen. Verify that there is visual feedback when response to any action takes more than 3

Splash should not remain for fore than 3 seconds. Application should display proper error message when device memory is low and exits gracefully from the situation. Clear key should navigate the user to previous screen. End Key should navigate the user to native OEM screen. There should be visual feedback given when response time for any

seconds. action is more than 3 second. Verify that continual key pad entry Continual key pad entry should not

do not cause any problem. cause any problem in application. Verify that user is able to exit from User should be able to exit with every application with every form of exit form of exit modes like modes like Flap,Slider,End Key or Flap,Slider,End Key or Exit option in Exit option in application and from any point. Verify that when application is

application and from any point. When application is running then

running then inserting and

inserting and removing charger

removing charger do not cause any problem and proper message

should not cause any problem and

is displayed when charger is

proper message should be displayed

inserted in device. Verify that when application is running and battery is low then proper message is displayed to the user. 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. Verify that application does not

when charger is inserted in device. When application is running and battery is low then proper message is displayed to the user telling user that battery is low. Removal of battery at the time of

consume battery excessively.

battery excessively.

application data call is going on should not cause interruption and data call should be completed after battery is inserted back in the device. The application should not consume

1. Find the application icon and Application must not take more than select it 2. “Press a button” on the device to launch the app. 3.Observe the application launch 25s to start. In the timeline defined Make sure that your application is Installed application should not cause not causing other applications of

other applications of device to

device to hamper. Application should gracefully

hamper. When the incoming communication enters the device the application must

handle the condition when incoming communication is made

at least respect one of the following: a) Go into pause state, after the user exits the communication, the

via Infra Red [Send a file using

application presents the user with a continue option or is continued

Infrared (if applicable) to the device application presents the

automatically from the point it was suspended at b) Give a visual or audible notification The application

user] Application should gracefully

must not crash or hung. When the incoming communication enters the device the application must

handle the condition when incoming communication is made

at least respect one of the following: a) Go into pause state, after the user exits the communication, the

via Infra Red [Send a file using

application presents the user with a continue option or is continued

Infrared (if applicable) to the device application presents the

automatically from the point it was suspended at b) Give a visual or audible notification The application

user]

must not crash or hung.

Application should gracefully

When the incoming communication enters the device the application must

handle the condition when incoming communication is made

at least respect one of the following: a) Go into pause state, after the user exits the communication, the

via Infra Red [Send a file using

application presents the user with a continue option or is continued

Infrared (if applicable) to the device application presents the

automatically from the point it was suspended at b) Give a visual or audible notification The application

user] Application should gracefully

must not crash or hung. When the incoming communication enters the device the application must

handle the condition when incoming communication is made

at least respect one of the following: a) Go into pause state, after the user exits the communication, the

via Infra Red [Send a file using

application presents the user with a continue option or is continued

Infrared (if applicable) to the device application presents the

automatically from the point it was suspended at b) Give a visual or audible notification The application

user]

must not crash or hung.

View more...

Comments

Copyright ©2017 KUPDF Inc.
SUPPORT KUPDF