test mobile

Upload: nguyen-hue

Post on 07-Apr-2018

225 views

Category:

Documents


0 download

TRANSCRIPT

  • 8/4/2019 Test Mobile

    1/13

    TEST 1 Installation: ci t

    TEST STEPS

    Before starting the test round, use a file manager to note the free user space available on the

    phone. You will need this information in test 8.Trc khi bt u thc hin vng kim th, s dng mt tp tin qun l phi ch khnggian trng ngi s dng trn in thoi. bn s cn nhng thng tin ny trong bi kim tra8

    1Install the application being tested. : Ci t ng dng bt u test

    The application must install without error.: ng dng ci t phi khng c li

    2

    During installation note the version number presented to the user. Trong khi ci t ch tiphin bn hin ti ca ngi s dng

    The version number must match that specified during submission. Phin bn s dng cn phiph hp vi quy trnh

    3

    Verify that the application has successfully installed on the device by navigating to the area onthe phone where new applications are installed.

    Xc minh rng ng dng ci t thnh cng trn thit b iu hng ti v tr trn in thoi,ni m ng dng mi c ci t

    The application should present one or more icon(s) on the phone.

    ng dng hin ti c mt hay nhiu biu tng trn in thoi

    Notes

    For any submissions which do not appear obviously once installed, the submitter must includedetails in the submission statement of how successful installation can be verified.

    Cho cc trnh m khng xut hin r rng mi khi ci t, ngi np phi c bao gm chi tittrong bo co np ca nhng ci t thnh cng c th chp nhn c

    If the content does not appear obviously on the device once installed, and specific instructions are

    lacking in the submission statement, then this test will be failed.

    Nu ni dung khng c xut hin r rng trn thit b mi khi c ci t, v hng dn chitit l thiu trong bo co, sau bi kim tra ny s b sai

    TEST 2 Application start/stop behaviour: hnh vi bt u/ kt thc ng dng

    TEST STEPS

  • 8/4/2019 Test Mobile

    2/13

    1

    Start the application by selecting the icon or following the steps outlined in the submissionstatement

    Bt u ng dng bng cc la chn biu tng hoc lm theo cc bc trong trnh bo cohng dn

    Navigate to the Task Manager and check that the application appears there.

    Chuyn hng qun l nhim v v kim tra xem ng dng c xut hin

    2

    Close the application from the Task Manager.

    ng ng dng t Task Manager

    Exit the Task Manager, and re-launch the Task Manager.

    Thot TM, v khi ng li TM

    The application must no longer appear in the Task Manager.

    ng dng phi khng cn xut hin trn TM

    3

    Start the application as in Step 1.

    Bt u ng dng nh bc 1

    Go to the Task Manager to verify that the application is running.

    i ti TM vi vic xc minh rng ng dng ang chy

    The application must appear in the task manager.

    ng dng phi xut hin trn thnh TM

    4

    Close the application from within the application UI and then return to the Task Manager.

    ng ng dng t trong giao din ng dng v sau tr v thanh TM

    The application must no longer be running and must no longer appear in the task manager.

    ng dng phi khng cn chy v phi khng xut hin trn thanh TM

    5 Restart the application as in Step 1.

    Khi ng li ng dng nh bc 1

  • 8/4/2019 Test Mobile

    3/13

    Navigate to the Task Manager.

    iu chnh thnh TM

    The application must once again appear in the Task Manager.

    ng dng phi mt ln na xut hin trn thanh TM

    Notes

    An application which must run in the background does not need to appear in the Task Manager orpresent a UI so long as the developer justifies this behaviour during submission.

    Mt ng dng m phi chy trn nn s k cn xut hin trn thanh TM hay hin ti ca mt giaodin di nh nh pht trin bin minh cho nhng hnh vi trong trnh

    All applications must have some way of verifying that they are running on the device, though, andthe developer should provide this information.

    Tt c ng dng phi c mt s cch xc minh rng chng ang chy trn thit b, mc d nhpht trin nn cung cp thng tin ny

    TEST 3 Application credentials: thng tin ng dng

    TEST STEPS

    1

    With the application running, check the name of the application displayed on the phone.

    Vi nhng ng dng ang chy, kim tra tn ca ng dng hin th trn in thoi

    The application must display the same name on the phone as stated during submission.

    ng dng phi hin th tn trn in thoi ging vi tn ng dng trong bo co

    2

    Note the functionality of the application as it runs on the device.

    Ch chc nng ca ng dng khi n chy trn thit b

    The basic functionality of the application must match that declared during submission.Chc nng c bn ca ng dng phi ph hp vi nhng tuyn b a ra trong bo co

    Notes

    Step 1 does not apply to applications which do not have a UI

  • 8/4/2019 Test Mobile

    4/13

    Bc 1 khng thc hin cho nhng ng dng m khng c giao din

    VoIP applications must present a UI in order to pass this test.

    ng dng VoIP phi trnh by mt giao din c th qua bi test ny

    TEST 4 No disruption to voice calls: khng c s gin on cuc gi

    TEST STEPS

    1

    With the application installed and running use a second phone to call the test device.

    Vi nhng ng dng ci t v ang chy, nn s dng in thoi th hai kim tra thitb

    The incoming call must be indicated to the user on the test device.

    Cc cuc gi ti phi ch ra cho ngi dng thy trn thit b kim tra

    2

    Answer the call on the test device.

    Tr li cuc gi trn thit b kim tra

    You must be able to conduct a conversation with the other party without interference fromthe application being tested.

    Bn cn phi c kh nng thc hin cuc tr chuyn vi bn kia m khng c s can thip t

    cc ng dng ang th nghim

    3

    End the call in the normal way on the test device.

    Kt thc cuc gi theo cch bnh thng trn thit b th nghim

    The voice call must be ended.

    Cuc gi phi c kt thc

    4 From the test device, make a call to a second phone. Answer the call from the other device.

    T thit b th nghim, to mt cuc gi ti in thoi th 2. Tr li cuc gi t cc thit bkhc

    The call must be indicated on both devices, and you must be able to conduct a conversationwith the other party without interference from the application being tested.

    Cuc gi phi c thc hin trn c hai thit b v bn phi c kh nng thc hin cuc tr

  • 8/4/2019 Test Mobile

    5/13

    chuyn vi bn kia m khng c s can thip t ng dng ang kim tra

    5

    End the voice call from the second device.

    Kt thc cuc gi t thit b th hai

    The call must be ended on both devices.

    Cuc gi phi c kt thc t c hai thit b

    6

    Place a test call to the emergency 112 number from the device.

    t cuc gi th nghim gi s khn cp 112 t thit b

    *Please check in your territory for the approved way to make test calls to the emergency

    services.Vui lng kim tra vng lnh th ca bn xem cch m to ra cuc gi th nghim thit bkhn cp

    Notes

    If the application being tested has the MultimediaDD capability, and has audio functionality, thenthat functionality must be in use whilst this test is performed. Particularly, it should be checkedthat the audio from the application is faded down to allow the user to hear the telephone call.

    VoIP applications will need this test running using both the handset held to the users ear and

    using a headset. The test should be run with a VoIP call in progress, and the incoming GSM callshould be announced with call waiting tones.

    TEST 5 No disruption to text messages: thng ip khng b gin on

    TEST STEPS

    1With the application installed and running, send a text message to the test device.

    The incoming text message must be notified to the user as per their alert settings.

    2

    Read the text message on the test device and choose to reply. Send the reply.

    The reply must be received at the second device.

    3

    From the standby screen on the test device, navigate to the new text message option andcreate a new message. Send the message to the second device.

    The message must be received at the second device.

  • 8/4/2019 Test Mobile

    6/13

    TEST 6 Auto-start behaviour: hnh vi t ng khi ng

    TEST STEPS

    1

    With the application running, find the settings for the application either within the

    application itself or from the settings option on the device.There must be an option which allows the user to enable/disable auto-start functionality.

    2Ensure that the setting for auto-start behaviour is disabled, and restart the device.

    The application must not start on device boot.

    3

    Now change the setting so that auto-start behaviour is enabled for the application and restart thephone.

    The application must start when the phone boots.

    Notes

    If the application does not have auto-start functionality, then this test does not need to be run.

    TEST 7- No disruption to key device applications: khng c s gin on ti cc thit b ngdng

    TEST STEPS

    1

    Ensure that the contacts, messaging and calendar applications are populated with data and startthe application as in Test 2.

    After the application has been installed and used, the data entered into those applications mustnot be altered in any way without the user being aware.

    2

    With the application running, navigate to the messages application and create a new message.

    Save that message to the drafts folder and then open and edit it.

    Finally, delete the message from the drafts folder and delete a message from the inbox.

    All of the above actions should be possible without interference from the installed application.

    3

    Navigate to the contacts application.

    Create a contact, then edit that contact and then delete it.

    The application should not interfere with any of the actions above without notifying the userand giving them option to avoid the change.

  • 8/4/2019 Test Mobile

    7/13

    4

    Navigate to the calendar application.

    Create an appointment in the calendar. Edit the appointment and then delete it.

    The application should not interfere with any of the actions above without notifying the user

    and giving them option to avoid the change.

    5

    Use the web browser on the device to go to a web page which is known to work on thenetwork being used.

    It must be possible to create a data connection and to access the web page selected.

    Notes

    If the application, as part of stated functionality, makes changes to user data then an exception canbe claimed here. The functionality must be described in the documentation with the applicationand all data other than that mentioned in the user guide must remain untouched as described in thetest case.

    The data used in this test case is also needed for Test 8, so leave the data on the device whenproceeding straight into Test 8.

    TEST 8 Un-install: g ci t

    TEST STEPS

    1

    Stop the application as described in Test 2 and uninstall the application using the systeminstaller.

    The application must be uninstalled without error.

    2

    Following the same steps as in Test 1, navigate to where you would expect to see theapplication icon.

    The application icon must not longer be present on the device.

    If you used another method to verify successful installation in Test 1 then use this method toensure that the application has been uninstalled.

    3

    Check the contacts, messages and calendar applications to ensure that that the data present in

    Test 7 is still present in those applications.

    4 Using the same file manager as at the start of Test 1 check that the amount of user spaceavailable on the device is either the same as that found in step 1 or that any difference betweenthe space available before and after fulfils the following criteria.

    a) Excluding user-generated and downloaded content, the application leaves no more than

  • 8/4/2019 Test Mobile

    8/13

    100Kb of data on the phone after uninstall

    b) Any data left on the device after install matches the explanation given during the submissionprocess

    Notes

    You should start this test with the application data from Test 7 still in place on the device.

    TEST 9 Device adaptation: thch ng thit b

    TEST STEPS

    Note: The following test steps should be run on the list of devices corresponding to the UIDsspecified in the .pkg file.

    1Install the application onto the deviceThe application should install on the device or present an error message to explain that itcannot install onto that device.

    2

    Launch the application.

    The application should run on the device or present an error message to explain that it cannotrun on that device.

    3

    Briefly examine the application whilst running.

    UI elements should be functional and text should be readable in the main screen of theapplication.

    4

    If the device on which the application is currently being tested supports portrait and landscapescreen modes, start the application and then switch between the screen modes.

    The application should continue to be functional, and usable, in both screen orientations of thedevice, whether or not the application rotates in response to the screen mode change.

    5Close the application from the application UI

    The application should stop running.

    6Uninstall the application from the phone.

    The un-installation should happen without error and the application must be un-installed.

    Notes

    Applications which do not present a UI to the user in normal usage do not need to run this test.

  • 8/4/2019 Test Mobile

    9/13

    On the primary device on which all of the other test cases have been run only step 4 of thistest should be performed as all of the other steps of this test case are covered elsewhere.

    Additional Tests for VoIP applicationsNote that Test 3 and Test 4 both contain additional notes which apply to the testing of VoIPapplications. Please read and apply these notes when running those tests on VoIP applications.

    Test 10 Additional emergency call testing for VoIP apps: th nghim vic thm cuc gikhn cp chi ng dng VoIP

    TEST STEPS

    Note: These test steps should be performed twice once with a SIM card in the device and

    once without.

    1

    With the VoIP application running in the background, but with no VoIP call in progress,initiate an emergency call in the usual way.

    The emergency call must be placed over the GSM/CDMA network successfully.

    2

    With the VoIP application running in the background with a VoIP call in progress, initiate anemergency call in the usual way.

    The emergency call must be placed over the GSM/CDMA network successfully and the VoIPcall should be terminated or placed on hold.

    3

    With the VoIP application in the background, and an emergency call active make a VoIP call tothe device.

    The incoming VoIP must be rejected, and the emergency call must not be interrupted.

    Share this: StumbleUpon Digg Reddit Email Facebook

    Testing Checklist for Mobile Applications

    http://mobileappstesting.com/2010/04/15/symbian-signed-tests-cases-v-4-0-14/?share=stumbleupon&nb=1http://mobileappstesting.com/2010/04/15/symbian-signed-tests-cases-v-4-0-14/?share=digg&nb=1http://mobileappstesting.com/2010/04/15/symbian-signed-tests-cases-v-4-0-14/?share=reddit&nb=1http://mobileappstesting.com/2010/04/15/symbian-signed-tests-cases-v-4-0-14/?share=email&nb=1http://mobileappstesting.com/2010/04/15/symbian-signed-tests-cases-v-4-0-14/?share=facebook&nb=1http://mobileappstesting.com/2009/10/23/testing-checklist-for-mobile-applications/http://mobileappstesting.com/2010/04/15/symbian-signed-tests-cases-v-4-0-14/?share=digg&nb=1http://mobileappstesting.com/2010/04/15/symbian-signed-tests-cases-v-4-0-14/?share=reddit&nb=1http://mobileappstesting.com/2010/04/15/symbian-signed-tests-cases-v-4-0-14/?share=email&nb=1http://mobileappstesting.com/2010/04/15/symbian-signed-tests-cases-v-4-0-14/?share=facebook&nb=1http://mobileappstesting.com/2009/10/23/testing-checklist-for-mobile-applications/http://mobileappstesting.com/2010/04/15/symbian-signed-tests-cases-v-4-0-14/?share=stumbleupon&nb=1
  • 8/4/2019 Test Mobile

    10/13

    October 23, 2009 Anurag Khode

    By-Anurag Khode,Copyright 2009-10

    No. Module Sub-

    Module

    Test Case Description Expected Result

    1 Installation Verify that application canbe Installed Successfully.

    Application should be able to installsuccessfully.

    2 Uninstallation Verify that application canbe uninstalled successfully.

    User should be able to uninstall theapplication successfully.

    3 Network TestCases

    Verify the behavior ofapplication when there isNetwork problem and useris performing operations

    for data call.

    User should get proper errormessage like Network error. Pleasetry after some time

    4 Verify that user is able toestablish data call whenNetwork is back in action.

    User should be able to establish datacall when Network is back in action.

    5 Voice CallHandling

    CallAccept

    Verify that user can acceptVoice call at the time whenapplication is running andcan resume back inapplication from the samepoint.

    User should be able to accept Voicecall at the time when application isrunning and can resume back inapplication from the same point.

    6 Call

    Rejection

    Verify that user can reject

    the Voice call at the timewhen application isrunning and can resumeback in application fromthe same point.

    User should be able to reject the

    Voice call at the time whenapplication is running and canresume back in application from thesame point.

    7 CallEstablish

    Verify that user canestablish a Voice call incase when application datacall is running inbackground.

    User should be able to establish aVoice call in case when applicationdata call is running in background.

    8 SMS Handling Verify that user can getSMS alert whenapplication is running.

    User should be able to get SMS alertwhen application is running.

    9 Verify that user can resumeback from the same pointafter reading the SMS.

    User should be able to resume backfrom the same point after reading theSMS.

  • 8/4/2019 Test Mobile

    11/13

    10 Unmapped keys Verify that unmapped keysare not working on anyscreen of application.

    Unmapped keys should not work onany screen of application.

    11 Application Logo Verify that application

    logo with ApplicationName is present inapplication manager anduser can select it.

    Application logo with Application

    name should be present inapplication manager and user canselect it.

    12 Splash Verify that when user selects application logo inapplication manager splashis displayed.

    When user selects application logoin application manager splash shouldbe displayed.

    13 Note that Splash do notremain for fore than 3seconds.

    Splash should not remain for forethan 3 seconds.

    14 Low Memory Verify that applicationdisplays proper errormessage when devicememory is low and exitsgracefully from thesituation.

    Application should display propererror message when device memoryis low and exits gracefully from thesituation.

    15 Clear Key Verify that clear keyshould navigate the user toprevious screen.

    Clear key should navigate the user toprevious screen.

    16 End Key Verify that End Key should

    navigate the user to nativeOEM screen.

    End Key should navigate the user to

    native OEM screen.

    17 Visual Feedback Verify that there is visualfeedback when response toany action takes more than3 seconds.

    There should be visual feedbackgiven when response time for anyaction is more than 3 second.

    18 ContinualKeypad Entry

    Verify that continual keypad entry do not cause anyproblem.

    Continual key pad entry should notcause any problem in application.

    19 Exit Application Verify that user is able toexit from application withevery form of exit modeslike Flap,Slider,End Key orExit option in applicationand from any point.

    User should be able to exit withevery form of exit modes likeFlap,Slider,End Key or Exit optionin application and from any point.

  • 8/4/2019 Test Mobile

    12/13

    20 Charger Effect Verify that whenapplication is running theninserting and removingcharger do not cause anyproblem and proper

    message is displayed whencharger is inserted indevice.

    When application is running theninserting and removing chargershould not cause any problem andproper message should be displayedwhen charger is inserted in device.

    21 Low Battery Verify that whenapplication is running andbattery is low then propermessage is displayed to theuser.

    When application is running andbattery is low then proper message isdisplayed to the user telling user thatbattery is low.

    22 Removal ofBattery

    Verify that removal ofbattery at the time ofapplication data call isgoing on do not causeinterruption and data call iscompleted after battery isinserted back in the device.

    Removal of battery at the time ofapplication data call is going onshould not cause interruption anddata call should be completed afterbattery is inserted back in the device.

    23 BatteryConsumption

    Verify that applicationdoes not consume batteryexcessively.

    The application should not consumebattery excessively.

    24 Application Start/Restart

    1. Find the application iconand select it 2. Press abutton on the device tolaunch the app. 3.Observethe application launch Inthe timeline defined

    Application must not take more than25s to start.

    25 Application SideEffects

    Make sure that yourapplication is not causingother applications of

    device to hamper.

    Installed application should notcause other applications of device tohamper.

  • 8/4/2019 Test Mobile

    13/13

    26 Externalincomingcommunication infrared

    Application shouldgracefully handle thecondition when incomingcommunication is made viaInfra Red [Send a file

    using Infrared (ifapplicable) to the deviceapplication presents theuser]

    When the incoming communicationenters the device the applicationmust at least respect one of thefollowing: a) Go into pause state,after the user exits the

    communication, the applicationpresents the user with a continueoption or is continued automaticallyfrom the point it was suspended at b)Give a visual or audible notificationThe application must not crash orhung.