Test Case Android

8/12/2019 Test Case Android

1/68


2/68

Test definitions

1 Install and Launch ....................................................................................... 41.1 OTA install ........................................................................................ 4

1.2 Long Launch Time ........................................................................... 52 Memor !se ................................................................................................. "

2.1 Memor during run .......................................................................... "# Connectivit ................................................................................................. $

#.1 Invalid %e& access setu' ................................................................ $#.2 (end)receive data............................................................................. *

#.# +et%or, dela s and loss of connection ......................................... -

#.4 +et%or, connectivit Air'lane mode ......................................... 104 /vent andling .......................................................................................... 114.1 Messaging auto start ..................................................................... 114.2 Message ueuing ........................................................................... 12

4.# Timed event e 'ir ......................................................................... 1#4.4 Timed event e 'ir during sus'end ............................................. 144.5 Timed event e 'ir during a''lication e it .................................. 15

5 Messaging 3 calls ...................................................................................... 1"5.1 (end ................................................................................................ 1"

5.2 eceive ........................................................................................... 1$5.# Incoming call .................................................................................. 1*

" / ternal Influence ...................................................................................... 1-".1 Memor card insertion ................................................................... 1-

".2 Memor card insertion and removal ............................................. 20".# Memor card screen &ehaviour..................................................... 21$ !ser Interface ............................................................................................. 22

$.1 eada&ilit ...................................................................................... 22$.2 ead time ........................................................................................ 2#$.# (creen re'ainting ........................................................................... 24$.4 Consistenc .................................................................................... 25$.5 e la out ease of use................................................................... 2"$." A''lication s'eed .......................................................................... 2$

$.$ /rror messages .............................................................................. 2*$.* 6unction 'rogress.......................................................................... 2-

$.- Actions %hile rendering................................................................. #0$.10 Multi'le dis'la format handling................................................... #1

$.11 7iffering screen si8es .................................................................... #2$.12 Multi'le format in'ut handling ...................................................... ##$.1# Accelerometer)motion sensor res'onses .................................... #4

$.14 ('elling errors................................................................................ #5$.15 Technical te t errors ...................................................................... #"

* Language .................................................................................................... #$*.1 Correct o'eration ........................................................................... #$

*.2 Manual selection ............................................................................ #**.# (u''orted formats ......................................................................... #-*.4 International characters................................................................. 40

- 9erformance ............................................................................................... 41-.1 (us'end)resume from main menu ................................................ 41-.2 (us'end %hile e ecuting............................................................... 42

-.# esume ........................................................................................... 4#-.4 Influence on terminal s stem features ......................................... 44

-.5 esource sharing : data&ase ........................................................ 4"10 Media .......................................................................................................... 4$

10.1 A''lication mute o'tion ................................................................ 4$10.2 (ettings statuses understanda&le ................................................ 4*10.# (ettings do not im'air a''lication ................................................ 4-10.4 (ettings com&inations ................................................................... 50


3/68

10.5 (aving settings............................................................................... 5110." ('ecific functions .......................................................................... 52

11 Menu ........................................................................................................... 5#11.1 el' and a&out ............................................................................... 5#

11.2 ;alid actions ................................................................................... 5512 6unctionalit .............................................................................................. 5"

12.1 6unctionalit sanit chec,............................................................. 5"12.2 A''lication hidden features .......................................................... 5$

1# e s ............................................................................................................ 5*1#.1 (crolling in menus ......................................................................... 5*

1#.2 (election ,e .................................................................................. 5-1#.# Te t field scrolling ......................................................................... "0

1#.4 9ause .............................................................................................. "11#.5 (imultaneous ,e 'resses ............................................................ "21#." Multi ,e 'resses ........................................................................... "#

14 7evice ('ecific Tests ................................................................................ "414.1 7evice close ................................................................................... "4

14.2 7evice o'en.................................................................................... "515 (ta&ilit ...................................................................................................... ""

15.1 A''lication sta&ilit ....................................................................... ""15.2 A''lication &ehaviour after forced close ..................................... "$

1" 7ata andling ............................................................................................ "*1".1 (ave game state ............................................................................. "*1".2 7ata deletion .................................................................................. "-

1".# Modif record ................................................................................. $01$ (ecurit ...................................................................................................... $1

1$.1 /ncr 'tion ...................................................................................... $11$.2 9ass%ords ...................................................................................... $2


4/68

1.1 OTA install

Test ID 1 .1

Test TitleLifec cle OTA install

Test Description T he A''lication must install via OTA.

Required for: A ll a''lications.

Testing Note1. If errors occur at installation time, corresponding messages must be reported

by the tester in the test report.2. If the device does not display the icon, then the user must be able to start the

Application using other means.3. For carriers that will only accept the installation of Applications from Android

Mar et, this test cannot be performed until the Application is in Android Mar et.

Testing Steps 1. !pen the browser Application of the device"

2. #ype the $%& of the Application file, or navigate to it graphically"

3. 'onnect to the typed $%& ( application icon" ). Accept the installation of the Application.

RESULT: 1. #he Application installs to the device. 2. #he icon for the Application can be found from the device.

Result of Test

9 A(( 6AIL


5/68

Test ID 1 .2

Test TitleLifec cle Long launch time

Test Description /nsure that the A''lication notifies the user a&out a long launch time.


Testing Note

Testing Steps 1. &aunch the Application. 2. !bserve launch time.

RESULT: If the Application ta es longer than * seconds to launch, a progress bar or a

message must be displayed to tell the user what is happening.Result of Test

9 A(( 6AIL


6/68

2.1 Memor during run

Test ID 2 .1

Test Title6ile ( stem Memor during run

Test Description /nsure that the A''lication correctl handles out of memor e ce'tions duringA''lication e ecution.

Required for:A''lication %hich %rites to file s stem.

Not required for: A''lication %hich does not %rite to file s stem.

Testing Note

Testing Steps 1. !perate the Application in such a way so as to force the Application to writefiles into the file system.

2. + it the Application. Fill the file system to its capacity or near it. 3. !perate the Application - try to e plore screens and functions, which accessthe file system.

RESULT: 1. #he Application should handle any out of memory e ceptions correctly. 2. +nsure that there is a warning to the user advising about lac of memory whenfile is trying to be stored.

Result of Test

9A(( 6AIL

/

A pplication does not write to file system.


7/68

#.1 Invalid %e& access setu'

Test ID # .1

Test Title TT9 Invalid +et%or, Connection

Test Description /nsure that the A''lication can handle the net%or, connection &einginvalid ) unusa&le.

Required for:A''lication using TT9 net%or, connection.

Not required for: A''lication not using TT9 net%or, connection.

Testing Note

Testing Steps1. Create and use an invalid !N entr"

- !pen ettings- /avigate to 0ireless 'ontrols Mobile /etwor s Access oint /ames.- 'reate a new A / with invalid details.

- ave this and select it with the radio button on the Access oint /ames screen.- + it the ettings menu

#. Launc$ t$e pplication

%. Initiate an &TT! net'or( connection fro) t$e pplication.

RESULT: # he Application should handle this situation and all e ceptions correctly.


8/68

Test ID # .2

Test Title TT9 (end)receive data

Test Description

/nsure that the A''lication can connect via a valid ?e& Access session setu'and send)receive data via an TT9 net%or, session.Required for:

A''lication using TT9 net%or, connection.Not required for:

A''lication not using TT9 net%or, connection.Testing Note

Testing Steps 1. 'reate a valid 0eb Access session setup. 2. &aunch the Application. 3. Initiate an ## networ connection from the Application.

). 'onduct some action which ensures a data transfer action via the /etwor

'onnection.

RESULT: 1. #he Application data is properly sent(received over the networ 4chec it for each

Application screen or feature that uses data services5.

Result of Test

9A(( 6AIL

/

A pplication does not use ## networ connection.


9/68

Test ID # .#

Test Title + et%or, connectivit : +et%or, dela sand the loss of connection

Test Description ?hen the A''lication uses net%or, ca'a&ilities@ it must &e a&le to handlenet%or, dela s and an loss of connection.

Required for:A''lication %hich uses +et%or, Connection.

Not required for: A''lication %hich does not use +et%or, Connection.

Testing Note

Testing Steps 1. &aunch the Application.

2. tart the networ access from the Application.

3. ut the phone in a place where there connection will be lost.

). !bserve the result.

RESULT: # he Application will wor until time out and then give an error message to the userindicating there was an error with the connection.

Result of Test

9A(( 6AIL

/

# he Application does not use /etwor 'onnection.


10/68

#.4 +et%or, connectivit Air'lane mode

Test ID # .4

Test Title + et%or, connectivit : Air'lane mode

Test Description ?hen the A''lication uses net%or, ca'a&ilities@ it must &e a&le to handlethe device &eing in Air'lane mode

Required for:A''lication %hich uses +et%or, Connection.

Not required for: A''lication %hich does not use +et%or, Connection.

Testing Note

Testing Steps 1. et the device to Airplane mode 2. tart the Application.

3. !bserve the result.

RESULT: # he Application will give a meaningful error message to indicate that the deviceis in Airplane mode and the application cannot run successfully.

Result of Test

9A(( 6AIL

/

# he Application does not use /etwor 'onnection.


11/68

4.1 Messaging auto start

Test ID 4 .1

Test Title M essaging Auto start and 'rocess

Test Description /nsure that the A''lication starts correctl on recei't of A''lications'ecific (M(

Required for:A''lication %hich is started & A''lication:s'ecific (M(.

Not required for: A''lication %hich is not started & A''lication:s'ecific (M(.

Testing Note

Testing Steps 1. +nsure that the Application is not running.

2. end an M message which meets the Application specification to the testhandset on the correct port number.

RESULT: 1. #he Application should launch correctly.

2. #he Application should process the incoming message correctly.Result of Test

9A(( 6AIL

/

# he Application does not use Application-specific M to start.


12/68

Test ID 4 .2

Test Title M essaging Message ueuing

Test Description /nsure that the A''lication ueues A''lication:s'ecific (M( messages for'rocessing.

Required for:A''lication %hich uses A''lication:s'ecific (M( messages.

Not required for: A''lication %hich does not use A''lication:s'ecific (M( messages.

Testing Note

Testing Steps%epeat test Messaging Auto start and 'rocess several times in 6uicsuccession.

RESULT: # he Application should 6ueue the messages and then correctly process the 6ueuedmessages.

Result of Test

9A(( 6AIL

/

# he Application does not use Application-specific M messages.


13/68

Test ID 4 .#

Test Title T imed /vent / 'ir during A''licationrun

Test Description /nsure that the A''lication &ehaves correctl on e 'ir of a timed event %hilethe A''lication is running.

Required for:A''lication %hich uses timed events.

Not required for: A''lication %hich does not use timed events.

Testing Note

Testing Steps 1 . et a timed event in the Application for a specific 7future8 time

2. 9eep the Application in an active state.

3. Allow the future time to pass.

RESULT: +n sure that Application reacts correctly once the designated time hase pired.

Result of Test

9A(( 6AIL

/

# he Application does not use timed events.


14/68

Test ID 4 .4

Test Title T imed /vent / 'ir during A''licationsus'end

Test Description /nsure that the A''lication resumes correctl from a sus'ended state one 'ir of a timed event.



Testing Note

Testing Steps 1. et a timed event in the Application for a specific 7future8 time

2. uspend the Application

3. Allow the future time to pass.

RESULT: +n sure that the application resumes correctly once the designated time hase pired, and then ensure that the Application behaves correctly after being resumed.

Result of Test

9A(( 6AIL

/



15/68

Test ID 4 .5

Test Title T imed /vent / 'ir during A''licatione it

Test Description /nsure that the A''lication starts correctl from an e ited state on e 'irof a timed event.



Testing Note

Testing Steps 1. et a timed event in the Application for a specific time

2. + it the Application

RESULT: 1. Application starts, or user is presented with a start option once thedesignated time has e pired. 2. Application behaves correctly when started.

Result of Test

9A(( 6AIL

/



16/68

5.1 (end

Test ID 5 .1

Test Title M essage (end

Test Description /nsure that the A''lication can send messages successfull .

Required for:A''lication %hich sends (M( or MM( messages as 'art of its functions.

Not required for: A''lication %hich does not send (M( or MM( messages as 'art of itsfunctions.

Testing Note

Testing Steps 1. &aunch Application. 2. end a message from the Application to another handset if both M

a nd MM are supported, test both formats.

RESULT: 1. /otification of new message is given where enabled on the receivinghandset. 2. Message is in the correct format, and for MM contains the correctpayload.

Result of Test

9A(( 6AIL

/

A pplication does not send messages as part of its functions.


17/68

Test ID 5 .2

Test Title M essage eceive

Test Description /nsure that the A''lication can receive messages successfull .

Required for:A''lication %hich receives (M( or MM( messages as 'art of itsfunctions.

Not required for: A''lication %hich does not receive (M( or MM( messages as 'art of itsfunctions.

Testing Note

Testing Steps 1. &aunch the Application 4with sound on5. 2. 'ompose message at another phone and send it to the test handset if theapplication supports both M and MM , test both formats.

RESULT: 1. /otification of new message is given where enabled on the receivinghandset. 2. Message is in the correct format, and for MM contains the correctpayload.

Result of Test

9A(( 6AIL

/

A pplication does not receive messages as part of its functions.


18/68

Test ID 5 .#

Test Title T ele'hone call incoming %hilea''lication in use

Test Description If the user acce'ts an incoming 'hone call %hile the A''lication is running@it should &e 'ossi&le to resume from the same 'oint in the A''lication atthe end of the call@ or a logical re:starting 'oint.


Testing Note

Testing Steps 1. 0hile Application is running, ma e an incoming call to the test handset. 2. Accept the incoming call.

3. +nd the incoming call. ). %eturn to the Application.

RESULT: 1. #he incoming call dialog is shown. 2. After the call is ta en and ended, the Application should resume to either the pointof interruption, or a point which neither inconveniences the user nor causes data loss.

Result of Test

9 A(( 6AIL


19/68

".1 Memor card insertion

Test ID " .1

Test Title M emor Card : Insertion

Test Description /nsure that the A''lication %or,s correctl follo%ing a memor cardinsertion action %hen the A''lication is sus'ended and resumed.

Required for:All a''lications@ on device %hich su''orts remova&le memor cards.

Not Required for:7evice %hich does not su''ort remova&le memor cards.

Testing Note


2. uspend Application

3. Insert the memory card into the phone, and mount the card. ). Fill the card to its capacity *. $nmount the memory card.

:. %esume and operate the Application

RESULT: # he Application continues to operate as designed based on the Applicationspecification and is not affected by the memory card insertion ormountin (unmountin .

Result of Test

9A(( 6AIL

/

7evice does not su''ort remova&le memor cards.


20/68

Test ID " .2

Test Title M emor Card Insertion and removal

Test Description /nsure that the A''lication %or,s correctl during a memor cardinsertion and removal.

Required for:All a''lications@ on device %hich su''orts remova&le memor cards.

Not Required for:7evice %hich does not su''ort remova&le memor cards.

Testing Note

Testing Steps 1. &aunch the Application. 2. Insert and remove the memory card.

3. ;erify that Application wor s correctly.

RESULT: 1. #he Application should wor correctly following memory card insertion. 2. #he Application should wor correctly with memory card removed.

Result of Test

9A(( 6AIL

/



21/68

Test ID " .#

Test Title M emor Card screen &ehaviour

Test Description /nsure that the A''lication %ith memor card functional screens %or,scorrectl %ith memor card inserted and removed.

Required for:A''lication %hich uses memor card.

Not Required for:1. 7evice %hich does not su''ort remova&le memor cardsB2. A''lication %hich does not use memor card@ regardless of device

su''ort.Testing Note

Testing Steps 1. &aunch the Application. 2. /avigate to screen where Application wor s with memory card.

3. Insert the memory card. ). ;erify that Application wor s correctly.

*. %emove the memory card. :. ;erify that Application wor s correctly.

RESULT: 1. #he Application should wor correctly following memory card insertion. 2. #he Application should wor correctly following memory card removal.

Result of Test

9A(( 6AIL

/


A''lication does not use memor card.


22/68

$.1 eada&ilit

Test ID

$ .1

Test Title

eada&ilitTest Description /nsure that the a''lication content is reada&le.

Required for:A''lications on all devices %ith user dis'la .

Not Required for: 7 evices %ithout user dis'la .

Testing Note An e ception to the re6uirement for na ed-eye legibility may be made where theapplications allows a high level graphical view of an item 4eg map or web page5 andthe device


23/68

Test ID $ .2

Test Title!I ead time

Test DescriptionComforta&le time for content reading.


Testing Note

Testing Steps$se the application, moving between screens.

RESULT: +a ch screen must be visible for the time necessary to comfortably read all itsinformation.

Result of Test

9 A(( 6AIL


24/68


25/68

Test ID $ .4

Test Title!I : Consistenc

Test Description!I consistenc .


Testing Note


RESULT: # he Application $I should be consistent and understandable throughout, e.g.common series of actions, action se6uences, terms, layouts, soft button definitionsand sounds that are clear and understandable

Result of Test

9 A(( 6AIL


26/68

Test ID $ .5

Test Title!I e la out ease of use

Test Descriptione la out ease of use.

Required for: A ll A''s.

Testing Note 1. 9ey layout ease of use should only be tested to the e tent that it can beinfluenced by the application. Any limitations of the device that cannot be overcomeby application design should be disregarded. 2. 0here the device offers multiple input methods 4e.g. hardware eypad ( t ouch screen eypad5, all the input methods available during normal use of theapplication should be tested.


RESULT: 1. #he buttons should be easy to use. 2. >utton usage should be suitable for both a left-handed and right-handed person,within the physical constraints of the device design.

Result of Test

9 A(( 6AIL


27/68

Test ID $ ."

Test Title!I : A''lication s'eed

Test Description T he A''lication %or,s in the device it %as targeted for@ and it is usa&le on thedevice the s'eed of the A''lication is acce'ta&le to the 'ur'ose of theA''lication and must not alter the user e 'erience & &eing uncontrolla&le.


Testing Note # he developer ( publisher is e pected to test the entire Application? for e ample, playthrough the entire game on the target handset. #he tester will only conduct arepresentative sample test of the Application in different areas if possible, for a 1*minutes period only.

Testing Steps

1. $se the Application. 2. !bserve how fast the Application is to use, and if it is too slow or too fast in itsoperation for good usability. 3. If the Application behavior is incontrollable due to its speed, please report suchfindings.

RESULT: 1. #he Application is usable on the device. 2. #he speed of the Application is good enough for the Application usage 4i.e. the

Application frame rate or response to user input must remain ade6uate, and must notcompromise the Application usage, or prevent the user from progressing normally5.

Result of Test

9 A(( 6AIL


28/68

Test ID $ .$

Test Title!I /rror messages

Test Description / rror messages.


Testing Note


RESULT: 1. Any error messages in the Application must be clearly understandable. 2. +rror messages must clearly e plain to a user the nature of the problem, andindicate what action needs to be ta en 4where appropriate5.

Result of Test

9 A(( 6AIL


29/68

Test ID $ .*

Test Title!I 6unction 'rogress

Test Description ; isual indication of the function e ecution 'rogress.


Testing Note


RESULT: 1. Any function selected in the Application should start within * seconds. 2. #here must be some visual indication that the function is being performed. 3. #he visual indication can be anything that the user would understand as aresponse, e.g.

- prompting for user input"- displaying splash screens or progress bars"- displaying te t such as 7 lease wait...8, etc.

Result of Test

9 A(( 6AIL


30/68

Test ID $ .-

Test Title!I Actions %hile rendering

Test Description A''lication must not 'erform ina''ro'riate actions %hile thin,ing orrendering


Testing Note

Testing Steps M a e user input while the Application or handset is busy processing orrendering.

RESULT: # here must be no inappropriate reaction by the Application.

Result of Test

9 A(( 6AIL


31/68

Test ID $ .10

Test Title!I Multi'le 7is'la 6ormat andling

Test Description ?here the device and A''lication can dis'la in multi'le formats =e.g. 'ortrait

) landsca'e@ internal ) e ternal dis'la >@ the elements of the a''lication should&e correctl formatted in all dis'la environments.

Required for:A''lications that su''ort multi'le dis'la formats@ on device %ithmulti'le dis'la formats su''ort.

Not required for:1. 7evice %hich does not have multi'le dis'la formatsB 2. A''lications that do not su''ort multi'le dis'la formats@ regardless ofdevice su''ort.

Testing Note*or t$is test+ a failure 'ould ,e a gross error t$at )a(es t$e application difficult touse+ or is seriousl" )isleading in so)e 'a". -inor errors t$at do

not i)pede functionalit" s$ould ,e passed+ ,ut t$e details added to t$e Result of Testinfor)ation as a te t note.

Testing Steps!perate the Application and ma e use of all available display formats in multiplefunctions.

RESULT: # he Application should display correctly without obvious errors in all formats.

Result of Test

9A(( 6AIL

/

7evice does not su''ort multi'le dis'la formats.

A''lication does not su''ort multi'le dis'la formats & design.


32/68

$.11 7iffering screen si8es

Test ID $ .11

Test Title!I 7iffering screen si8es

Test Description ?here the a''lication is designed to %or, on multi'le devices it must &e a&leto dis'la correctl on differing screen si8es

Required for:A''lications that su''ort multi'le devices

Not required for: A''lications that target s'ecific devices

Testing Note*or t$is test+ a failure 'ould ,e t$e ina,ilit" to displa" correctl" on devices 'it$different screen si/es.

Testing Steps!perate the Application on two devices with differing screen si


33/68

Test ID $ .12

Test Title!I Multi'le 6ormat In'ut andling

Test Description ?here the device and a''lication can acce't in'ut in multi'le formats =e.g.e ternal touchscreen ) e ternal ,e 'ad ) internal touchscreen ) internal ,e 'ad

) ?/ TD la out ) 12:,e la out and others>@ the a''lication must %or,correctl %ith all su''orted in'ut methods.

Required for:A''lications that su''ort multi'le in'ut formats@ on device %ith multi'le in'utformat su''ort.

Not required for:1. 7evice %hich does not have multi'le in'ut formatsB 2. A''lications that do not su''ort multi'le in'ut formats@ regardless of devicesu''ort.

Testing Note*or t$is test+ a failure 'ould ,e a gross error t$at )a(es t$e application difficult to

use+ or is seriousl" )isleading in so)e 'a". -inor errors t$at donot i)pede functionalit" s$ould ,e passed+ ,ut t$e details added to t$e Result of Testinfor)ation as a te t note.

Testing Steps!perate the Application and ma e use of all input methods in all functions.

RESULT: # he Application should accept input correctly in all supported formats.

Result of Test

9A(( 6AIL

/

7evice does not su''ort multi'le in'ut formats.

A''lication does not su''ort multi'le in'ut formats & design.


34/68

Test ID $ .1#

Test Title!I Accelerometer ) Motion (ensor

es'onsesTest Description

T he res'onse of the a''lication to movement or change of alignment of thedevice should not im'air use of the a''lication@ nor &e li,el to confuse theuser.

Required for:All A''lications@ e ce't %here &oth device and A''lication lac,accelerometer ) motion sensor su''ort.

Not required for: A''lication %here &oth it and the device lac, accelerometer ) motion sensorsu''ort.

Testing Note 1. #esting should be performed even where either the device or the Application 4but

not both5 lac accelerometer support, in order to determine any une pected reactionto the presence or absence of motion sensor responses. 2. Minor hesitations or inaccuracies are permissible. #o fail, the problems must beserious enough to ma e it difficult to use the application. 3. #he device could have ad=ustable orientation 4accelerometer rotation5 found in ettings@ ound Bisplay@Bisplay ettings. #ry chec ing the bo labelled7!rientation8 to switch orientation automatically when rotating phone.

Testing Steps!perate the Application and ma e use of functions while changing the position,angle and alignment of the device and sub=ecting it to slow, rapid, and randommovements.

RESULT: # he response of the application to movement or change of alignment of the deviceshould not impair use of the application, nor be li ely to confuse the user. Applicationshould change between portrait and landscape modes without confusing errorsbeing displayed to user.

Result of Test

9A(( 6AIL

/

7evice not e ui''ed %ith accelerometer ) motion sensor. A''lication

does not ma,e use of accelerometer ) motion sensor.


35/68

Test ID $ .14

Test Title!I : ('elling errors

Test Description T he A''lication must &e free of s'elling errors.


Testing Note1. A spelling error is defined as a strict mis-spelling of a word 4no grammar or

punctuation rules will be applied5. Missing diacritics and accents 4e.g. acutes,cedillas, umlauts etc5 will not be reported as spelling errors.

2. #he tester will perform the test as specified below, but the developer must ensurethat this re6uirement is fulfilled throughout the Application.

3. In all cases, spelling shall be acceptable if it conforms to the norm for a selectedlanguage or location.

). For generic +nglish, $ spelling is to be regarded as the norm, but >ritish spellingwill be acceptable so long as the chosen spelling is used

throughout.

Testing Steps1. &aunch Application in target language.2. 'hec te t appearing in?

a5 plash(#itle(&ogo(&oading creen"b5 Main Menu and all its subsidiary menus"c5 elp(Instructions creen4s5"d5 About screen"e5 Application ause Menu and all its subsidiary menus 4if present5.

RESULT:

/o spelling errors must be present in the defined areas.Result of Test

9 A(( 6AIL


36/68

Test ID $ .15

Test Title!I : Technical te t errors

Test DescriptionThe te t in the A''lication must &e clear and reada&le. T he A''lication must &e free of technical te t dis'la issues such as Te tcut off ) Te t overla''ing.


Testing Note1. #he tester will perform the test as specified below, but the developer must ensure

that this re6uirement is fulfilled throughout the Application.2. All te t in each target language is displayed without corruption, distortion or other

display problems. + amples of failures may include?a5 Menu item te t labels incorrectly aligned with cursor"b5 >utton te t label over-running the button area or truncated such that its

meaning is not clear"

c5 #e t over-running or being truncated in other bounded te t display areas4e.g. speech bubbles, user interface elements etc5"

d5 #e t not wrapping at the edge of the screen resulting in words beingcut off"

e5 Multiple pieces of te t overlapping each other, or te t overlapping userinterface elements 4but see note 3 below5"

f5 #e t being cut hori


37/68

*.1 Correct o'eration

Test ID

* .1

Test Title

Language Correct o'erationTest Description /nsure that the A''lication %or,s correctl %ith all a''ro'riatelanguages.


Testing Note 1. #ranslation table with all te t used in $I should be provided to #est team beforetesting starts.

Testing Steps 1. If handset supports more than one language, set handset to a language not alreadytested in certification testing. 2. &aunch the Application and perform brief testing with aim to go through all possiblescreens, menu, messages. 3. If Application pecification specifies that Application detects selected h andset language, ensure Application displays appropriate for eachsupported language. ). + it the Application *. %epeat steps 1 to ) for each supported language.

RESULT: 1. All te t content is rendered in the correct(e pected language. 2. +nsure Application detects correct language and renders content asappropriate 4if applicable5.

Result of Test

9 A(( 6AIL


38/68

Test ID * .2

Test TitleLanguage Manual selection

Test Description /nsure that the A''lication allo%s selection of languages.

Required for:A''lication %hich allo%s selection of languages %ithin the A''lication.

Not Required for:A''lication that does not 'ermit selection of languages %ithin the A''lication.

Testing Note

Testing Steps 1. et Application to each language using language selection facility of the

Application. 2. erform brief testing.

RESULT: 1. $ser is able to select all desired languages. 2. All te t content is rendered in the correct(e pected language.

Result of Test

9A(( 6AIL

/

A''lication does not 'ermit selection of languages.


39/68

Test ID * .#

Test TitleLanguage (u''orted formats

Test Description /nsure that the A''lication su''orts all date)time)numeric)currencfeatures for su''orted languages


Testing Note

Testing Steps ;erify that date, time, time


40/68

Test ID * .4

Test TitleLanguage International characters

Test Description /nsure that the A''lication acce'ts and dis'la s all a''ro'riateinternational characters correctl .


Testing Note

Testing Steps ;erify that all data entry fields accept and properly display all Internationalcharacters.

RESULT: All international te t characters are rendered in the correct(e pectedlanguage.

Result of Test

9 A(( 6AIL


41/68

-.1 (us'end)resume from main menu

Test ID - .1 Test TitleLifec cle (us'end ) resume from mainmenu

Test Description /nsure that the A''lication sus'ends %hen at the A''lication main menu.


Testing Note


2. Do to the main menu of the Application. 3. uspend the Application

). %esume the Application

RESULT: Application should suspend and resume correctly, and resume at a point that doesnot impair the user e perience.

Result of Test

9 A(( 6AIL


42/68

Test ID - .2

Test TitleLifec cle (us'end %hile e ecuting

Test DescriptionChec, for (us'end in the middle of A''lication e ecution.


Testing Note

Testing Steps 1. &aunch the Application. 2. Buring Application e ecution, suspend the Application 3. %esume the Application

RESULT: Application should suspend and resume correctly, and resume at a point that doesnot impair the user e perience.

Result of Test

9 A(( 6AIL


43/68

Test ID - .#

Test TitleLifec cle : esume

Test Description /nsure that the A''lication resumes correctl .


Testing Note # he ob=ective of this test is to confirm the applicationCs stability when suspendedand resumed multiple times from different locations in one test cycle.

Testing Steps 1. erform Lifec cle (us'end ) resume from main menu 2. %esume the Application ). erform Lifec cle (us'end %hile e ecuting

*. %epeat step 2.

RESULT:

# he Application resumes to the point where it was suspended, or to a point thatdoes not impair the user e perience.

Result of Test

9 A(( 6AIL


44/68

Test ID - .4

Test TitleLifec cle : Influence on Terminal ( stem6eatures

Test DescriptionA''lication must correctl handle situations %here follo%ing user in'ut@ orsome e ternal event =e.g. a 'hone call>@ it is s%itched to the &ac,ground & theterminal. !'on returning to foreground the A''lication must resume itse ecution correctl . ?hile in the &ac,ground the A''lication must not emit anaudio =unless it is 'art of its s'ecific 'ur'ose to do so> and all handset functionsshould remain intact. ?hile &eing in the &ac,ground@ the A''lication must either not affect the useof the s stem features or other A''lications or@ if the A''lication does so@ such&ehaviour must &e descri&ed in the hel' file.

Not Required for:A''lication %hich is not %ritten to run as a (ervice.

Required for: A''lication %hich is %ritten to run as a (ervice.Testing Note

1. 0hen performing the test below, the Application either needs to be switched tobac ground or foreground. #he actual method used depends on the functionality ofthe target terminal 2. If features are found to be disabled or not able to be used and are not listed in thehelp file the Application must fail this test. 3. #he developer should be as ed whether the Application is written to run asa ervice, and the answer should determine whether this test is applicable.


2. Familiari


45/68

Test ID - .4

Test TitleLifec cle : Influence on Terminal ( stem6eatures

E. ;erify that the Application operates normally by using it for a time period of * minutes.

RESULT: 1. #erminalCs system features and Applications can be used normally 2. In case the Application e ecution causes some changes to normal use of systemfeatures and Applications, this is ade6uately e plained in the help file of the

Application. 3. After the Application is brought bac to foreground, it continues to operatenormally.

Result of Test

9A(( 6AIL

/

A''lication is not %ritten to run as a (ervice.


46/68

Test ID - .5

Test TitleLifec cle : esource (haring 7ata&ase

Test DescriptionChec, that data&ase resources are 'ro'erl shared &et%een A''lication and acom'eting A''lication.

Required for:A''lications %hich ma,e use of Contacts data&ase.

Not required for: A''lications %hich do not ma,e use of Contacts data&ase.

Testing Note Application under test should not be the device native 'ontacts application.


2. uspend Application

3. &aunch the device 'ontacts application

). Add a new entry into contacts. *. %emove an e isting entry from contacts. :. %esume the Application under test E. 'hec Application state.

RESULT: 1. Application should continue from the previous state prior to beingsuspended. 2. A lication should see the new entr and the deleted entr .

Result of Test

9A(( 6AIL

A''lication does not use Contacts data&ase.


47/68

10.1 A''lication mute o'tion

Test ID

10 .1

Test Title

M edia A''lication mute o'tionTest Description /nsure that the A''lication has a Mute or (ound On ) Off setting.

Required for:A''lications %ith sound settings.

Not Required for: A''lication %hich is declared not to have a A''lication mute facilit & design.

Testing Note It will be sufficient for the application to respect the settings of the device volumecontrols, such that sound can be turned down to


48/68

Test ID 10 .2

Test Title M edia (ettings statusesunderstanda&le

Test Description /nsure that the A''lication settings statuses are easil understanda&le.

Required for:A''lications %hich have (ettings o'tions.

Not required for: A''lications %hich do not have (ettings o'tions.

Testing Note

Testing Steps 1. tart the application. 2. 'hange the status of settings

RESULT:

# he current status of each setting must be easily understood.

Result of Test

9A(( 6AIL

/

A''lication does not have an settings o'tions.


49/68

Test ID 10 .#

Test TitleMedia (ettings do not im'air A''lication

Test DescriptionThe status of the A''lication settings does not im'air the A''licationfunctionalit .



Testing Note

Testing Steps1. tart the application2. 'hange settings3. !bserve the result.

RESULT: # he current status of the settings does not affect the Application operation 4e.g.whether or not the sound is on in a game5. For e ample, switching off the sounddoes not chan e the ame s functionalit .

Result of Test

9A(( 6AIL

/



50/68

Test ID 10 .4

Test Title M edia (ettings com&inations

Test Descriptionestrictive com&inations of A''lication settings is not 'ermitted.



Testing Note

Testing Steps). tart the application*. 'hange settings:. !bserve the result.

RESULT:

+a ch setting has separate enable(disable functionality 4e.g. ;ibration and ound5. Any combinations of settings 4e.g., ;ibration and ound5 should not limit the userCschoice so as to e clude specific combinations.

Result of Test

9A(( 6AIL

/



51/68

Test ID 10 .5

Test Title M edia (aving settings

Test Description /nsure that the A''lication saves all settings on e it.


Not required for:1. A''lications %hich do not have (ettings o'tionsB 2. A''lications %hich do not save changes to (ettings & design.

Testing Note

Testing Steps1. tart the application2. 'hange an item in settings3. + it and restart the application

). !bserve the setting status

RESULT: 0 hen an Application e its, all settings must be saved.%estarting the Application will restore the saved settings.

Result of Test

9A(( 6AIL

/


A''lication is declared not to save settings on close & design.


52/68

Test ID 10 ."

Test Title Media ('ecific functions

Test Description /nsure A''lication sounds have s'ecific functions and should not &e overutilised.

Required for:A''lications %ith sound.

Not required for: A''lications %ithout sound.

Testing Note

Testing Steps$se the application and observe the sounds utilised

RESULT: +a ch sound should have a specific function, and should not be over used

4e.g. game completing with a minute of random noise is not permitted5.

Result of Test

9A(( 6AIL

/

A''lication does not have an sounds.


53/68

11.1 el' and a&out

Test ID 11 .1

Test Title Menu (tructure el' 3 A&out items

Test Description T he A''lication should contain standard Menu items el' 3 A&out.

Required for:A''lications %ith user interface ca'a&le of dis'la ing information to user.

Not required for: A''lications %ithout user interface ca'a&le of dis'la ing information to user.

Testing Note 1 It is a re6uirement that applications with a user interface should contain 3elpinformation, to e plain to the user how the Application wor s" and About information,so that the user can easily identify the e act version of the Application installed, thedeveloper of the Application, and the developer contact details.

Testing Note # # his test can be passed if the application contains the information in #esting /ote 1and it is easy to access, even if the items are not named e actly as in the test steps.#he tester should indicate in their report if the application has passed this test on avalue =udgement li e this, rather than a literal interpretation of the test steps.

Testing Note % If it is clear that the applicationCs purpose re6uires networ coverage to operate, then itwill be sufficient for the elp to be provided through a browser connection rather thanbeing contained in the application. In the opposite case, where most functions of theapplication can be used while the device is offline, then the application should have

elp that can be accessed without needing a data connection.Testing Note 2

0 here the amount or type of elp information appears insufficient for easy use of theapplication, the tester should give specific instances in their report.

Testing Steps1. tart the application2. Access the elp and About sections

RESULT: 1. Menu items li e elp and About are re6uired to be presented on the main menu orother easily-found screen of the Application. Ab out functions should contain the Application version number and author information. 2. elp should include the aim of the Application, usage of the eys 4e.g. for games5and other instructions. If the te t of the help is too long, it should be divided intosmaller sections and(or organi


54/68

Test ID 1# .2

Test Titlee 9ress (election ,e

Test Description (e lection ,e selects menu items.

Required for:A''lications %ith user interaction.

Not required for: A''lications %ithout user interaction.

Testing Note

Testing Steps 1. &aunch the Application. 2. ress the primary selection ey or device e6uivalent in the main menu item list.

RESULT: # his M$ # select the menu item with no adverse effects on the Application.

Result of Test

9A(( 6AIL

/

A''lication does not have user interaction & design.


55/68


56/68

Test ID 1# .4

Test Titlee 9ress 9ause

Test DescriptionThe A''lication must su''ort a 'ause feature in areas of the A''lication %hereimmediate user interaction is needed =for e am'le in game>. T he 'ause feature must su''ort an o'tion to resume the A''lication@ andan o'tion to go &ac, to the main menu of the A''lication.

Required for:A''lications re uiring time:sensitive user interaction.

Not Required for:1. A''lications %here immediate user intervention is not needed =fore am'le timer A''lication>B 2. A''lications %ithout user interaction.

Testing Note # he developer is encouraged to use the available A Is for pause and

continue methods.

Testing Steps 1. &aunch the Application. 2. $se the Application and its features.

3. 'hec that the user can pause the Application at any time if so desired. ). 'hec that the Application can also be Gun-pausedG.

RESULT: 1. #he user can pause the Application and the pause feature must support an optionto resume . 2. All time-specific features of the Application are disabled at the time of the pause. 3. #here is a clear indication that the Application is in a paused state.

). #here is a clear indication how the user can return from the paused state.

Result of Test

9A(( 6AIL

/

A''lication does not re uire immediate user intervention.



57/68

Test ID 1# .5

Test Titlee 9ress (imultaneous ,e 'resses

Test Description /nsure that the A''lication co'es %ith simultaneous ,e 'resses.

Required for:A''lications %ith user interaction.

Not required for: A''lications %ithout user interaction.

Testing Note

Testing Steps 1. &aunch the Application. 2. ress combinations of eys simultaneously, from a selection of $ , B!0/, &+F#,%ID #, '+/#+% and all other available eys, e cepting any which intentionallyterminate or e it the application, or intentionally launch a function that wouldinvalidate the test.

RESULT: # he Application should not be put into an unusable or incomprehensible state bysimultaneous ey presses. Any error messages generated should be meaningful.

Result of Test

9A(( 6AIL

/



58/68

Test ID 1# ."

Test Titlee 9ress Multi ,e 'resses

Test Description If device and a''lication su''ort multi ,e 'ress o'eration@ these should'erform as e 'ected.

Required for:A''lication that su''orts multi ,e 'ress actions@ on device that alsosu''orts this.

Not required for: A''lication or device %ithout su''ort for multi ,e 'ress.

Testing Note

Testing Steps 1. &aunch the Application. 2. $se the multi ey press actions as documented by the developer in the

elp, or documented separately.

RESULT: All reactions to multi ey presses should be as predicted by the documentationand should not leave the Application in an unusable state.

Result of Test

9A(( 6AIL

/


A''lication does not su''ort multi ,e 'ress.

7evice does not su''ort multi ,e 'ress.


59/68

14 7evice ('ecific Tests

14.1 7evice close

Test ID

14 .1

Test Title

Action : 7evice CloseTest Description /nsure that the A''lication %hile launching handles closing of the devicecorrectl .

Required for:A''lications on devices %ith o'en ) close functionalit .

Not Required for:7evice %ithout o'en ) close functionalit .

Testing Note

Testing Steps 1. &aunch the Application. 2. 0hile the Application is launching 4i.e. G lease wait8 screen5, close the deviceand then 3-) times 6uic ly open and close it. 3. !pen the device.

RESULT: # he Application returns to the same state before the interruption.

Result of Test

9A(( 6AIL

/

7evice does not have o'en ) close functionalit .


60/68

14.2 7evice o'en

Test ID 14 .2

Test Title Action 7evice O'en

Test Description /nsure that the A''lication handles device o'ening correctl .

Required for:A''lications on devices %ith o'en ) close functionalit .

Not Required for:7evice %ithout o'en ) close functionalit .

Testing Note

Testing Steps 1. &aunch the Application. 2. $se the Application and its features. 3. 'lose the device.

). !pen the device.

RESULT: # he Application returns to the same state before the interruption.Result of Test

9A(( 6AIL

/

7evice does not have o'en ) close functionalit .


61/68

15 (ta&ilit

15.1 A''lication sta&ilit

Test ID

15 .1

Test Title

(ta&ilit A''lication sta&ilitTest Description T he A''lication must not crash or free8e at an time %hile running on thedevice.


Testing Note 1. Buring any time of the testing observe the Application behavior. 2. #he report must indicate if the error can be reproduced or not.

Testing Steps 1. tart to test the Application. 2. !bserve the Application behavior during the testing.

RESULT: # he Application must not free


62/68

15.2 A''lication &ehavior after forced close

Test ID 15 .2

Test Title (ta&ilit A''lication &ehavior afterforci&le close & ( stem

Test Description A''lication must 'reserve sufficient state information to co'e %ithforci&le close & the s stem.


Testing Note If it is not possible to remove the device battery, a power cycle should be forcedwith the device power ey instead.

Testing Steps 1. tart the Application. 2. + ercise the functionality of the application, including any function that buildsor saves information. 3. ress the ome ey to return to the ome screen and ensure the

application is switched into a paused state. ). %emove the battery to instantly ill the application, as the system does whendealing with a low memory situation. *. %estart the handset and open the application again. :. 'hec the application is in a usable state and any information built or savedbefore the close has been retained.

RESULT: # he Application must not lose any information that it implies would be preserved,nor become difficult to use subse6uently, as a result of a forcible closure by thesystem.

Result of Test

9 A(( 6AIL


63/68

1" 7ata andling

1".1 (ave game state

Test ID

1" .1

Test Title

(a ve record Eame stateTest Description /nsure that the A''lication can save its game state)high score ta&leinformation into 'ersistent memor .

Required for:1. A''lication %here user ma e it 'art com'leted gameB

2. A''lication %here a 'la er high score value is identified.Not Required for:

A''lication %hich does not have game state ) high score elements.Testing Note

Testing Steps 1. &aunch the Application and start a game. 2. >ring up the game menu and e it saving game position. 3. %un Application again and continue game.

). lay game until a high score is obtained.

*. >ring up game menu and chec igh score table. :. + it Application and restart. E. 'hec high score table.

RESULT: 1. Dame state should be as was immediately prior to Application e it.

2. #he high score table should represent the scores recorded during the

A lication test.Result of Test

9A(( 6AIL

/

A''lication does not have game state or high score elements.


64/68

Test ID 1" .2

Test Title7elete 7ata deletion

Test Description T he A''lication must indicate %hether data %ill &e 'ermanentl deleted oroffer eas reversal of the deletion.

Required for:A''lication %hich has function to delete data.

Not required for: A''lication %hich does not have function to delete data.

Testing Note # he user should always be re6uired to confirm deletion of data, or have an optionto undo deletion, to reduce ris of accidental loss of information through user error.

Testing Steps 1. &aunch the Application. 2. $se the function which deletes something on the Application. 3. 'hec if there is a reversal 4undo5 available for the user or that the user is notified

before deletion is permanent.RESULT: 1. >efore the data deletion, the Application notified the user of deletion, or the Application has an 7undo8 feature. 2. If 7undo8 is present it wor s as e pected.

Result of Test

9A(( 6AIL

/

A''lication does not have function to delete data.


65/68

Test ID 1" .#

Test Title Modif ecord

Test Description /nsure that the A''lication can modif its game state)high score ta&leinformation into 'ersistent memor .

Required for:1. A''lication %hich ma &e e ited 'art:%a through game 'la B2. A''lication %hich identifies a user high score value.

Not Required for: A''lication %hich does not have game state ) high score elements.

Testing Note%epeating the save of game state and high score ensures that the values initiallysaved can be updated.

Testing Steps %epeat (ave record Eame state

RESULT:3a)e state is saved4updated

Result of Test

9A(( 6AIL

/

A''lication does not have game state ) high score elements.


66/68

1$ (ecurit

1$.1 /ncr 'tion

Test ID

1$ .1

Test Title

(ecurit /ncr 'tionTest Description ?hen connections are used encr 'tion is used for sending ) receivingsensitive data.

Required for:A''lication identified as communicating sensitive data.

Not Required for: A''lication identified as not communicating sensitive data.

Testing Note All sensitive information 4personal data, credit card ban ing information etc.5must be encrypted during transmission over any networ or communication lin .

Testing Steps%efer to supplied information about the application. If the application transmitssensitive data and the developer has not stated encryption is used, this test cannot bepassed

RESULT: It has been declared that the Application uses encryption whencommunicating sensitive data.

Result of Test

9A(( 6AIL

/

A''lication is stated not to communicate sensitive data.


67/68

1$.2 9ass%ords

Test ID 1$ .2

Test Title (ecurit 9ass%ords

Test Description 9ass%ords or other sensitive data are not stored in the device and are notechoed %hen entered into the A''lication@ sensitive data is al%a s 'rotected& 'ass%ord.

Required for:A''lication %hich uses 'ass%ords or other sensitive data.

Not Required for: A''lication %hich does not use 'ass%ords or other sensitive data.

Testing Note1. 0 ith passwords the desired approach is that the Application shows which

character the user selected and then changes that to an asteris 4H5.2. If the user is e plicitly as ed for permission, a password can be stored to the

device memory.3. #he ob=ective of the test is to minimian (credit card account numbers, balances access codes or passwords should betreated as sensitive and be protected from unrestricted access.

Testing Steps 1. &aunch the Application. 2. Do to the section where passwords or other sensitive data 4such as credit carddetails5 is input or displayed. 3. Input or read some sensitive data. !bserve how the data are displayed on t he screen. ). + it the Application.

*. &aunch the Application. :. Do to the place where sensitive data was inserted or read. E. ee if the data is still visible, or can be redisplayed without re6uiring apassword at any point.

RESULT: 1. +ntering a password or other sensitive data will not leave it in clear te t ifcompletion of the fields is interrupted but not e ited. 2. asswords, credit card details, or other sensitive data do not remain in clearte t in the fields where they were previously entered, when the application is re-entered. 3. ensitive personal data should always need entry of a password before it can beaccessed.


68/68

Test Case Android

Documents