UTI Testing Criteria (UTC)

for Android applications

V1.1: June 2012

This is the UTI Testing Criteria (UTC) for Android applications.

Applications passing the appropriate tests will be deemed by the Unified Testing Initiative to
be of a high quality standard.
Please read the following information - sections 1, 2 and 3 - before looking at the individual
tests in section 4).

Section 1. Testing notes

The tests should be performed on a device to which a factory reset has been applied prior to
the installation of the application to be tested. This will ensure that there is a known base
with only pre-installed applications and any errors will be attributable to the application under
test.
It is not within the scope of these criteria to be able to test the performance of the application
on devices with multiple applications installed.
If an application uses another application to perform a function (such as the Facebook
application for accessing Facebook details) it should be tested as if the application
performed that function itself. In this way the user experience is tested as a complete endto-end solution and the correct use of the other application is tested as well.

Section 2. Different types of apps and their associated tests

The tests within the UTC (see section 4) have been developed to test different features of
different apps.
Not all tests have to be conducted for every type of app.
This section describes the different types of apps and the tests to be carried out for each
type.
Introduction
Mobile applications are tested for a number of reasons, chief among these are the needs to
protect the customer and the vendor from software which does not work properly or exhibits
malicious behaviour. The variety of applications is huge and is growing daily so there is a
clear need to tailor testing to the level of complexity. To address this we have defined
applications to be either Simple or Complex.
There are over 100 different permissions that can be requested by an application so it is
highly unlikely that any applications will not make some form of permission request. There is
also going to be a high proportion of connected applications as developers will be targeting
the advanced capabilities of the device and its always- connected state. This also means
that functionality that would be deemed complex in some other technologies is simple in
Android e.g. connecting to a server to pull down information on weather or sports scores.
We therefore would deem accessing many of the permissions as still being the behaviours of
a simple application.

Simple App definition and tests

A Simple Android Application would be one which;

Does not send SMS/MMS

Does not write data to standard data files e.g. contacts, calendar
Does not write data to external services e.g. social networks.
Can access but does not change the state of networking services e.g.
3G/Wifi/Bluetooth
Can access external sites to retrieve information
Can access location information
Can read standard data files
Can read SMS/MMS
Can access screen, sound, camera, keyboard.
Can write its own data e.g. store pictures, create documents.

This list is not exhaustive as new application types are being developed all the time but will
cover 90% of applications.
A simple Android application will require the following tests to be carried out;
Test

1.1
1.2
3.1
3.4
5.2
5.3
6.1
7.1
7.3
7.5
7.8
7.10
7.11
7.12
7.14
7.15
8.1
8.3
9.1
9.2
10.1
11.1
12.1
13.1
13.3
15.1
15.2
16.2

Title

OTA Install
Long launch time
Send/Receive Data
Resource downloading
Message Receive
Incoming call
Memory card operation
Readability
Screen Repainting
Key Layout ease of use
Function progress
Multiple display format handling
Different screen sizes
Multiple format input handling
Spelling errors
Technical text errors
Language correct operation
Language supported formats
Suspend/resume from main menu
Suspend/resume while executing
Application Mute option
Help and About
Functionality Sanity Check
Scrolling in menus
Pause
Application Stability
Application behaviour after forced close
Data Deletion

Framework app definition and tests

There are many applications where the same application framework is used repeatedly to
create new applications. This is especially prevalent for dictionaries, books and magazine
applications but may occur in any application genre.
For these applications it is clearly excessive to fully test the new application as it is to a large
degree an existing application with new resource files. For these applications the appropriate
criteria (simple or complex) should be used in the first instance and then the following tests
are to be performed for subsequent derived applications.
Test
1.1
3.1
3.4
7.1
11.1
12.1
15.1

Title
OTA Install
Send/Receive Data
Resource downloading
Readability
Help and About
Functionality Sanity Check
Application Stability

Complex Applications
Any application which does not fall into the above categories i.e. Framework or Simple will
be deemed to be Complex and will be subject to testing against the full criteria.

Smoke Test
Wikipedia defines a Smoke Test as a first test made after assembly or repairs to a system,
to provide some assurance that the system under test will not catastrophically fail.
The Smoke Test is a very basic set of tests that is suitable to confirm that a tested app runs
(at least at a basic level) on a subsequent device. The Smoke Test can be used to confirm
basic handset compatibility, but does not guaranteed full functionality.
Test cases to be carried out for a Smoke Test:
Test
1.1
1.2
7.1
11.1
15.1
15.2

Title
OTA Install
Long Launch Time
Readability
Help and about
Application Stability
Application behaviour after forced close

Section 3: critical tests, warning tests and levels of warning

We recognise that many of the tests that are performed do not produce a binary result. They
are often subjective leaving the interpretation to the tester. It is unfair therefore to fail an
application for one minor error that may be down to a testers opinion.
To account for this, the individual tests in the criteria below are each marked as either
Critical and Warning.
Critical Tests
As the name suggests, a Critical test must be passed.
If an application fails the test then the application has an overall fail.
Warning Tests
For a test which is considered Warning, we have allowed for four different results; pass,
annoying, difficult and impossible.
These warning levels are described as follows;

Pass = the app has passed the test. There are no issues
Annoying = a minor error has occurred with the app - e.g. one or two typos that
would make the application not perfect but still very useable
Difficult = a more serious issue has occurred with the app e.g. multiple typos making
the application difficult to use but not impossible
Impossible = a very serious issue has occurred with the app - the errors are so bad
as to make the application unusable.

Once all appropriate tests have been carried out, points should be attributed according to the
following scale.
Warning levels:

Annoying = 1 points
Difficult = 2 points

Impossible = 4 points

Critical levels:

5 points

For an application to pass, the errors should not add up to more than 3 points.
4 points or more is a failure.
(As an example, an application could have 3 annoying results, or 1 difficult and 1 annoying
and still pass.)

Section 4: the tests

1 Install and Launch .................................................................................... 8
1.1
OTA install .................................................................................................... 8
1.2
Long Launch Time ....................................................................................... 9
2 Memory Use .......................................................................................... 10
2.1
Memory during run .................................................................................... 10
3 Connectivity .......................................................................................... 11
3.1
Send/Receive Data ..................................................................................... 11
3.2
Network delays and loss of connection ................................................... 12
3.3
Network connectivity Airplane mode .................................................... 13
3.4
Network connectivity - resource downloading ........................................ 14
4 Event Handling....................................................................................... 15
4.1
Messaging auto start ................................................................................. 15
4.2
Message queuing ....................................................................................... 16
4.3
Timed event expiry .................................................................................... 17
4.4
Timed event expiry during suspend ......................................................... 18
4.5
Timed event expiry during application exit .............................................. 19
5 Messaging & calls ................................................................................... 20
5.1
Send ............................................................................................................ 20
5.2
Receive ....................................................................................................... 21
5.3
Incoming call .............................................................................................. 22
6 External Influence ................................................................................... 23
6.1
Memory card operation ............................................................................. 23
6.2
Memory card screen behaviour ................................................................ 24
7 User Interface ........................................................................................ 25
7.1
Readability.................................................................................................. 25
7.2
Read time.................................................................................................... 26
7.3
Screen repainting....................................................................................... 27
7.4
Consistency ............................................................................................... 28
7.5
Key layout ease of use .............................................................................. 29
7.6
Application speed ...................................................................................... 30
7.7
Error messages .......................................................................................... 31
7.8
Function progress ..................................................................................... 32
7.9
Actions while rendering ............................................................................ 33
7.10 Multiple display format handling .............................................................. 34
7.11 Differing screen sizes ................................................................................ 35
7.12 Multiple format input handling .................................................................. 36
7.13 Accelerometer/motion sensor responses ................................................ 37
7.14 Spelling errors ........................................................................................... 38
7.15 Technical text errors .................................................................................. 39
8 Language .............................................................................................. 40
8.1
Correct operation ....................................................................................... 40
8.2
Manual selection ........................................................................................ 41
8.3
Supported formats ..................................................................................... 42
8.4
International characters ............................................................................ 43
9 Performance .......................................................................................... 44
9.1
Suspend/resume from main menu............................................................ 44
9.2
Suspend while executing .......................................................................... 45
9.3
Resume ....................................................................................................... 46
9.4
Influence on terminal system features ..................................................... 47
9.5
Resource sharing - database .................................................................... 49

10 Media ................................................................................................. 50
10.1 Application mute option ............................................................................ 50
10.2 Settings statuses understandable ............................................................ 51
10.3 Settings do not impair application............................................................ 52
10.4 Saving settings .......................................................................................... 53
10.5 Specific functions ...................................................................................... 54
11 Menu .................................................................................................. 55
11.1 Help and about ........................................................................................... 55
11.2 Valid actions............................................................................................... 57
12 Functionality ........................................................................................ 58
12.1 Functionality sanity check ........................................................................ 58
12.2 Application hidden features ...................................................................... 59
13 Keys ................................................................................................... 60
13.1 Scrolling in menus ..................................................................................... 60
13.2 Text field scrolling ..................................................................................... 61
13.3 Pause .......................................................................................................... 62
13.4 Simultaneous key presses or multiple touch .......................................... 63
13.5 Multi key presses or multi touch............................................................... 64
14 Device Specific Tests ............................................................................. 65
14.1 Device close ............................................................................................... 65
14.2 Device open................................................................................................ 66
15 Stability .............................................................................................. 67
15.1 Application stability ................................................................................... 67
15.2 Application behaviour after forced close ................................................. 68
16 Data Handling....................................................................................... 69
16.1 Save game state ......................................................................................... 69
16.2 Data deletion .............................................................................................. 70
16.3 Modify record ............................................................................................. 71
17 Security .............................................................................................. 72
17.1 Encryption .................................................................................................. 72
17.2 Passwords .................................................................................................. 73

Install and Launch

1.1

OTA install

Test ID
Test Title
Critical
1.1
Lifecycle OTA install
Test Description
The Application must install via OTA.
Required for:
All applications.
Testing Note
1. 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
Market, this test cannot be performed until the Application is in Android
Market.
Testing Steps
1. Open the browser Application of the device;
2. Type the URL of the Application file, or navigate to it graphically;
3. Connect to the typed URL / application icon;
4. Accept the installation of the Application.
RESULT:
1. The Application installs to the device.
2. The icon for the Application can be found from the device.
Result of Test
PASS

FAIL

1.2

Long Launch Time

Test ID
Test Title
Critical
1.2
Lifecycle Long launch time
Test Description
Ensure that the Application notifies the user about a long launch time.
Required for:
All applications.
Testing Note
Testing Steps
1. Launch the Application.
2. Observe launch time.
RESULT:
If the Application takes longer than 5 seconds to launch, a progress bar or a
message must be displayed to tell the user what is happening.
Result of Test
PASS

FAIL

Memory Use
2.1

Memory during run

Test ID
Test Title
Critical
2.1
File System Memory during run
Test Description
Ensure that the Application correctly handles out of memory exceptions
during Application execution.
Required for:
Application which writes to file system.
Not required for:
Application which does not write to file system.
Testing Note
Testing Steps
1. Operate the Application in such a way so as to force the Application to
write files into the file system.
2. Exit the Application. Fill the file system to its capacity or near it.
3. Operate the Application - try to explore screens and functions, which
access the file system.
RESULT:
1. The Application should handle any out of memory exceptions correctly.
2. Ensure that there is a warning to the user advising about lack of memory
when file is trying to be stored.
Result of Test
PASS

FAIL

EXCEPTION(S)
Application does not write to file system.

10

Connectivity
3.1

Send/Receive Data

Test ID
Test Title
Critical
3.1
HTTP Send/receive data
Test Description
Ensure that the Application can connect via a valid Web Access session
setup and send/receive data via an HTTP network session.
Required for:
Application using HTTP network connection.
Not required for:
Application not using HTTP network connection.
Testing Note
Where the application uses a different application to perform the data transfer
e.g. Facebook, Flickr etc,. it still needs to be tested to ensure end to end
functionality.
Testing Steps
1. Create a valid Web Access session setup.
2. Launch the Application.
3. Initiate an HTTP network connection from the Application.
4. Conduct some action which ensures a data transfer action via the Network
Connection.
RESULT:
1. The Application data is properly sent/received over the network (check it for
each Application screen or feature that uses data services).
Result of Test
PASS

FAIL

EXCEPTION(S)
Application does not use HTTP network connection.

11

3.2

Network delays and loss of connection

Test Title
Critical
Network connectivity - Network delays and
the loss of connection
Test Description
When the Application uses network capabilities, it must be able to handle
network delays and any loss of connection.
Required for:
Application which uses Network Connection.
Not required for:
Application which does not use Network Connection.
Testing Note
Where the application uses a different application to perform the data transfer
e.g. Facebook, Flickr etc,. it still needs to be tested to ensure end to end
functionality.
Test ID
3.2

Testing Steps
1. Launch the Application.
2. Start the network access from the Application.
3. Put the phone in a place where there connection will be lost.
4. Observe the result.
RESULT:
The Application will work until time out and then give an error message to the
user indicating there was an error with the connection.
Result of Test
PASS

FAIL

EXCEPTION(S)
The Application does not use Network Connection.

12

3.3

Network connectivity Airplane mode

Test ID
Test Title
Critical
3.3
Network connectivity - Airplane mode
Test Description
When the Application uses network capabilities, it must be able to handle
the device being in Airplane mode
Required for:
Application which uses Network Connection.
Not required for:
Application which does not use Network Connection.
Testing Note
Where the application uses a different application to perform the data transfer
e.g. Facebook, Flickr etc,. it still needs to be tested to ensure end to end
functionality.
Testing Steps
1. Set the device to Airplane mode
2. Start the Application.
3. Observe the result.
RESULT:
The Application will give a meaningful error message to indicate that the device
is in Airplane mode and the application cannot run successfully.
Result of Test
PASS

FAIL

EXCEPTION(S)
The Application does not use Network Connection.

13

3.4

Network connectivity - resource downloading

Test Title
Critical
Network connectivity - resource
downloading
Test Description
When the Application uses network capabilities to download resource files
it must be able to handle pause and resume and interruptions to
downloads
Required for:
Application which uses downloadable resource files
Not required for:
Application which does not use downloadable resource files.
Testing Note
Where the application uses a different application to perform the data transfer
e.g. Facebook, Flickr etc,. it still needs to be tested to ensure end to end
functionality.
Test ID
3.4

Testing Steps
Start the Application.
Start a resource file download
Pause the download if possible
Restart the download
Drop the network connection
Recreate the network connection
Resume/restart the download
RESULT:
The Application will gracefully handle the pausing, stopping and resumption of
resource file downloads.
Result of Test
PASS

FAIL

EXCEPTION(S)
The Application does not use downloadable resource files.

14

Event Handling
4.1

Messaging auto start

Test ID
Test Title
Critical
4.1
Messaging Auto start and process
Test Description
Ensure that the Application starts correctly on receipt of Application
specific SMS
Required for:
Application which is started by Application-specific SMS.
Not required for:
Application which is not started by Application-specific SMS.
Testing Note
Testing Steps
1. Ensure that the Application is not running.
2. Send an SMS message which meets the Application specification to the test
handset on the correct port number.
RESULT:
1. The Application should launch correctly.
2. The Application should process the incoming message correctly.
Result of Test
PASS

FAIL

EXCEPTION(S)
The Application does not use Application-specific SMS to start.

15

4.2

Message queuing

Test ID
Test Title
Critical
4.2
Messaging Message queuing
Test Description
Ensure that the Application Queues Application-specific SMS messages for
processing.
Required for:
Application which uses Application-specific SMS messages.
Not required for:
Application which does not use Application-specific SMS messages.
Testing Note
Testing Steps
Repeat test Messaging Auto start and process several times in quick
succession.
RESULT:
The Application should queue the messages and then correctly process the
queued messages.
Result of Test
PASS

FAIL

EXCEPTION(S)
The Application does not use Application-specific SMS messages.

16

4.3

Timed event expiry

Test Title
Critical
Timed Event Expiry during Application
run
Test Description
Ensure that the Application behaves correctly on expiry of a timed event
while the Application is running.
Required for:
Application which uses timed events.
Not required for:
Application which does not use timed events.
Testing Note
Test ID
4.3

Testing Steps
1.Set a timed event in the Application for a specific future time
2. Keep the Application in an active state.
3. Allow the future time to pass.
RESULT:
Ensure that Application reacts correctly once the designated time has expired.
Result of Test
PASS

FAIL

EXCEPTION(S)
The Application does not use timed events.

17

4.4

Timed event expiry during suspend

Test Title
Critical
Timed Event Expiry during Application
suspend
Test Description
Ensure that the Application resumes correctly from a suspended state on
expiry of a timed event.
Required for:
Application which uses timed events.
Not required for:
Application which does not use timed events.
Testing Note
Test ID
4.4

Testing Steps
1. Set a timed event in the Application for a specific future time
2. Suspend the Application
3. Allow the future time to pass.
RESULT:
Ensure that the application resumes correctly once the designated time has
expired, and then ensure that the Application behaves correctly after being
resumed.
Result of Test
PASS

FAIL

EXCEPTION(S)
The Application does not use timed events.

18

4.5

Timed event expiry during application exit

Test Title
Critical
Timed Event Expiry during Application
exit
Test Description
Ensure that the Application starts correctly from an exited state on expiry
of a timed event.
Required for:
Application which uses timed events.
Not required for:
Application which does not use timed events.
Testing Note
Test ID
4.5

Testing Steps
1. Set a timed event in the Application for a specific time
2. Exit the Application
RESULT:
1. Application starts, or user is presented with a start option once the designated
time has expired.
2. Application behaves correctly when started.
Result of Test
PASS

FAIL

EXCEPTION(S)
The Application does not use timed events.

19

Messaging & calls

5.1

Send

Test ID
Test Title
Critical
5.1
Message Send
Test Description
Ensure that the Application can send messages successfully.
Required for:
Application which sends SMS or MMS messages as part of its functions.
Not required for:
Application which does not send SMS or MMS messages as part of its
functions.
Testing Note
Testing Steps
1. Launch Application.
2. Send a message from the Application to another handset if both SMS and
MMS are supported, test both formats.
RESULT:
1. Notification of new message is given where enabled on the receiving handset.
2. Message is in the correct format, and for MMS contains the correct payload.
Result of Test
PASS

FAIL

EXCEPTION(S)
Application does not send messages as part of its functions.

20

5.2

Receive

Test ID
Test Title
Critical
5.2
Message Receive
Test Description
Ensure that the Application can receive messages successfully.
Required for:
Application which receives SMS or MMS messages as part of its functions.
Not required for:
Application which does not receive SMS or MMS messages as part of its
functions.
Testing Note
Testing Steps
1. Launch the Application (with sound on).
2. Compose message at another phone and send it to the test handset if the
application supports both SMS and MMS, test both formats.
RESULT:
1. Notification of new message is given where enabled on the receiving handset.
2. Message is in the correct format, and for MMS contains the correct payload.
Result of Test
PASS

FAIL

EXCEPTION(S)
Application does not receive messages as part of its functions.

21

5.3

Incoming call

Test Title
Critical
Telephone call incoming while
application in use
Test Description
If the user accepts an incoming phone call while the Application is running,
it should be possible to resume from the same point in the Application at
the end of the call, or a logical re-starting point.
Required for:
All applications.
Testing Note
Test ID
5.3

Testing Steps
1. While Application is running, make an incoming call to the test handset.
2. Accept the incoming call.
3. End the incoming call.
4. Return to the Application.
RESULT:
1. The incoming call dialog is shown.
2. After the call is taken and ended, the Application should resume to either the
point of interruption, or a point which neither inconveniences the user nor causes
data loss.
Result of Test
PASS

22

FAIL

External Influence
6.1

Memory card operation

Test ID
Test Title
Warning
6.1
Memory Card Insertion & Removal
Test Description
Ensure that the Application works correctly following memory card
insertion and removal.
Required for:
All applications, on device which supports removable memory cards.
Not Required for:
Device which does not support removable memory cards.
Testing Note
Testing Steps
1. Launch the Application.
2. Suspend Application
3. Insert the memory card into the phone, and mount the card.
4. Fill the card to its capacity
5. Unmount the memory card.
6. Resume and operate the Application
RESULT:
The Application continues to operate as designed based on the Application
specification and is not affected by the memory card insertion or
mounting/unmounting.
Result of Test
PASS

FAIL

EXCEPTION(S)
Device does not support removable memory cards.

23

6.2

Memory card screen behaviour

Test ID
Test Title
Critical
6.2
Memory Card screen behaviour
Test Description
Ensure that the Application with memory card functional screens works
correctly with memory card inserted and removed.
Required for:
Application which uses memory card.
Not Required for:
1. Device which does not support removable memory cards;
2. Application which does not use memory card, regardless of device
support.
Testing Note
Testing Steps
1. Launch the Application.
2. Navigate to screen where Application works with memory card.
3. Insert the memory card.
4. Verify that Application works correctly.
5. Remove the memory card.
6. Verify that Application works correctly.
RESULT:
1. The Application should work correctly following memory card insertion.
2. The Application should work correctly following memory card removal.
Result of Test
PASS

FAIL

EXCEPTION(S)
Device does not support removable memory cards.
Application does not use memory card.

24

User Interface
7.1

Readability

Test ID
Test Title
Warning
7.1
Readability
Test Description
Ensure that the application content is readable.
Required for:
Applications on all devices with user display.
Not Required for:
Devices without user display.
Testing Note
An exception to the requirement for naked-eye legibility may be made where
the applications allows a high level graphical view of an item (eg map or web
page) and the device zoon facility is used to make areas legible, providing
that usability is not impaired by any limiting of the visible areas when zoomed
sufficiently to be legible.
Testing Steps
All screen content must be clear (e.g. screen not crowded with content) and
readable to the naked eye regardless of information displayed, or choice of
font, colour scheme etc.
RESULT:
The application content should be readable. If there are issues they should be
graded according to the scale in the results box.
Result of Test
Pass

Annoying

EXCEPTION(S)
Device does not have user display

25

Difficult

Impossible

7.2

Read time

Test ID
Test Title
7.2
UI Read time
Test Description
Comfortable time for content reading.
Required for:
All applications.
Testing Note

Warning

Testing Steps
Use the application, moving between screens.
RESULT:
Each screen must be visible for the time necessary to comfortably read all its
information. If the screen is not visible for an appropriate time the issue should be
graded.
Result of Test
Pass

Annoying

26

Difficult

Impossible

7.3

Screen repainting

Warning

Test ID
Test Title
7.3
UI Screen repainting
Test Description
Correct screen repainting.
Required for:
All applications.
Testing Note
Testing Steps
Use the application, moving between screens.

RESULT:
1. The Application screens must be correctly repainted, including cases when
edit boxes and dialog boxes are dismissed.
2. There must be no blinking of moving objects and background. If the
Application objects overlap they must still render correctly.
Result of Test
Pass

Annoying

27

Difficult

Impossible

7.4

Consistency

Warning

Test ID
Test Title
7.4
UI - Consistency
Test Description
UI consistency.
Required for:
All applications.
Testing Note
Testing Steps
Use the application, moving between screens.

RESULT:
The Application UI should be consistent and understandable throughout, e.g.
common series of actions, action sequences, terms, layouts, soft button
definitions and sounds that are clear and understandable
Result of Test
Pass

Annoying

28

Difficult

Impossible

7.5

Key layout ease of use

Test ID
Test Title
Warning
7.5
UI Key layout ease of use
Test Description
Key layout ease of use.
Required for:
All Apps.
Testing Note
1. Key layout ease of use should only be tested to the extent that it can be
influenced by the application. Any limitations of the device that cannot be
overcome by application design should be disregarded.
2. Where the device offers multiple input methods (e.g. hardware keypad / touch
screen keypad), all the input methods available during normal use of the
application should be tested.
Testing Steps
Use the application, moving between screens.
RESULT:
1. The buttons should be easy to use.
2. Button usage should be suitable for both a left-handed and right-handed
person, within the physical constraints of the device design.
Result of Test
Pass

Annoying

29

Difficult

Impossible

7.6

Application speed

Test ID
Test Title
Warning
7.6
UI - Application speed
Test Description
The Application works in the device it was targeted for, and it is usable on
the device: the speed of the Application is acceptable to the purpose of the
Application and must not alter the user experience by being uncontrollable.
Required for:
All applications.
Testing Note
The developer / publisher is expected to test the entire Application: for example,
play through the entire game on the target handset. The tester will only conduct a
representative sample test of the Application in different areas if possible, for a
15 minutes period only.
Testing Steps
1. Use the Application.
2. Observe how fast the Application is to use, and if it is too slow or too fast in its
operation for good usability.
3. If the Application behavior is incontrollable due to its speed, please report such
findings.
RESULT:
1. The Application is usable on the device.
2. The speed of the Application is good enough for the Application usage (i.e. the
Application frame rate or response to user input must remain adequate, and must
not compromise the Application usage, or prevent the user from progressing
normally).
Result of Test
Pass

Annoying

30

Difficult

Impossible

7.7

Error messages

Warning

Test ID
Test Title
7.7
UI Error messages
Test Description
Error messages.
Required for:
All applications.
Testing Note
Testing Steps
Use the application, moving between screens.

RESULT:
1. Any error messages in the Application must be clearly understandable.
2. Error messages must clearly explain to a user the nature of the problem, and
indicate what action needs to be taken (where appropriate).
Result of Test
Pass

Annoying

31

Difficult

Impossible

7.8

Function progress

Test ID
Test Title
Warning
7.8
UI Function progress
Test Description
Visual indication of the function execution progress.
Required for:
All applications.
Testing Note
Testing Steps
Use the application, moving between screens.
RESULT:
1. Any function selected in the Application should start within 5 seconds.
2. There must be some visual indication that the function is being performed.
3. The visual indication can be anything that the user would understand as a
response, e.g.
- prompting for user input;
- displaying splash screens or progress bars;
- displaying text such as Please wait..., etc.
Result of Test
Pass

Annoying

32

Difficult

Impossible

7.9

Actions while rendering

Test ID
Test Title
Warning
7.9
UI Actions while rendering
Test Description
Application must not perform inappropriate actions while thinking or
rendering
Required for:
All applications.
Testing Note
Testing Steps
Make user input while the Application or handset is busy processing or rendering.
RESULT:
There must be no inappropriate reaction by the Application.
Result of Test
Pass

Annoying

33

Difficult

Impossible

7.10 Multiple display format handling

Test ID
Test Title
Warning
7.10
UI Multiple Display Format Handling
Test Description
Where the device and Application can display in multiple formats (e.g.
portrait / landscape, internal / external display), the elements of the
application should be correctly formatted in all display environments.
Required for:
Applications that support multiple display formats, on device with
multiple display formats support.
Not required for:
1. Device which does not have multiple display formats;
2. Applications that do not support multiple display formats, regardless
of device support.
Testing Note
For this test, a failure would be a gross error that makes the application
difficult to use, or is seriously misleading in some way. Minor errors that do
not impede functionality should be passed, but the details added to the Result
of Test information as a text note.
Testing Steps
Operate the Application and make use of all available display formats in
multiple functions.
RESULT:
The Application should display correctly without obvious errors in all formats.
Result of Test
Pass

Annoying

Difficult

Impossible

EXCEPTION(S)
Device does not support multiple display formats.
Application does not support multiple display formats by design.

34

7.11 Differing screen sizes

Test ID
Test Title
Warning
7.11
UI Differing screen sizes
Test Description
Where the application is designed to work on multiple devices it must
be able to display correctly on differing screen sizes
Required for:
Applications that support multiple devices
Not required for:
Applications that target specific devices
Testing Note
For this test, a failure would be the inability to display correctly on devices
with different screen size..
Android defines screen sizes as small, normal, large and extra large. Support
for these sizes is defined in the application manifest.
Testing Steps
Operate the Application on two devices with differing screen sizes.
RESULT:
The Application should display correctly without obvious errors.
Result of Test
Pass

Annoying

Difficult

Impossible

EXCEPTION(S)
Application does not support multiple devices. This can be determined from
the APK manifest

35

7.12 Multiple format input handling

Test ID
Test Title
Critical
7.12
UI Multiple Format Input Handling
Test Description
Where the device and application can accept input in multiple formats (e.g.
external touch screen / external keypad / internal touch screen / internal
keypad / QWERTY layout / 12-key layout and others), the application must
work correctly with all supported input methods.
Required for:
Applications that support multiple input formats, on device with multiple
input format support.
Not required for:
1. Device which does not have multiple input formats;
2. Applications that do not support multiple input formats, regardless of
device support.
Testing Note
For this test, a failure would be a gross error that makes the application difficult to
use, or is seriously misleading in some way. Minor errors that do not impede
functionality should be passed, but the details added to the Result of Test
information as a text note.
Testing Steps
Operate the Application and make use of all input methods in all functions.
RESULT:
The Application should accept input correctly in all supported formats.
Result of Test
PASS

FAIL

EXCEPTION(S)
Device does not support multiple input formats.
Application does not support multiple input formats by design.

36

7.13 Accelerometer/motion sensor responses

Test Title
Warning
UI Accelerometer / Motion Sensor
Responses
Test Description
The response of the application to movement or change of alignment of
the device should not impair use of the application, nor be likely to
confuse the user.
Required for:
All Applications, except where both device and Application lack
accelerometer / motion sensor support.
Not required for:
Application where both it and the device lack accelerometer / motion
sensor support.
Testing Note
1. Testing should be performed even where either the device or the
Application (but not both) lack accelerometer support, in order to determine
any unexpected reaction to the presence or absence of motion sensor
responses.
2. Minor hesitations or inaccuracies are permissible. To fail, the problems
must be serious enough to make it difficult to use the application.
3. The device could have adjustable orientation (accelerometer rotation)
found in Settings\Sound & Display\Display Settings. Try checking the box
labelled Orientation to switch orientation automatically when rotating phone.
Test ID
7.13

Testing Steps
Operate the Application and make use of functions while changing the
position, angle and alignment of the device and subjecting it to slow, rapid,
and random movements.
RESULT:
The response of the application to movement or change of alignment of the
device should not impair use of the application, nor be likely to confuse the
user. Application should change between portrait and landscape modes
without confusing errors being displayed to user.
Result of Test
Pass

Annoying

Difficult

Impossible

EXCEPTION(S)
Device not equipped with accelerometer / motion sensor.
Application does not make use of accelerometer / motion sensor.

37

7.14 Spelling errors

Test ID
Test Title
Warning
7.14
UI - Spelling errors
Test Description
The Application must be free of spelling errors.
Required for:
All applications.
Testing Note
1. A spelling error is defined as a strict mis-spelling of a word (no grammar or
punctuation rules will be applied). Missing diacritics and accents (e.g. acute
accents, cedillas, umlauts etc) will not be reported as spelling errors.
2. The tester will perform the test as specified below, but the developer must
ensure that this requirement is fulfilled throughout the Application.
3. In all cases, spelling shall be acceptable if it conforms to the norm for a
selected language or location.
4. For generic English, US spelling is to be regarded as the norm, but British
spelling will be acceptable so long as the chosen spelling is used throughout.
Testing Steps
1. Launch Application in target language.
2. Check text appearing in:
a) Splash/Title/Logo/Loading Screen;
b) Main Menu and all its subsidiary menus;
c) Help/Instructions Screen(s);
d) About screen;
e) Application Pause Menu and all its subsidiary menus (if present).
RESULT:
No spelling errors must be present in the defined areas.
Result of Test
Pass

Annoying

38

Difficult

Impossible

7.15 Technical text errors

Test ID
Test Title
Warning
7.15
UI - Technical text errors
Test Description
The text in the Application must be clear and readable.
The Application must be free of technical text display issues such as: Text
cut off / Text overlapping.
Required for:
All applications.
Testing Note
1. The tester will perform the test as specified below, but the developer must
ensure that this requirement is fulfilled throughout the Application.
2. All text in each target language is displayed without corruption, distortion or
other display problems. Examples of failures may include:
a) Menu item text labels incorrectly aligned with cursor;
b) Button text label over-running the button area or truncated such that
its meaning is not clear;
c) Text over-running or being truncated in other bounded text display
areas (e.g. speech bubbles, user interface elements etc);
d) Text not wrapping at the edge of the screen resulting in words being
cut off;
e) Multiple pieces of text overlapping each other, or text overlapping user
interface elements (but see note 3 below);
f) Text being cut horizontally.
3. Text overlapping user interface elements may be allowable where
a) The developer has stated that this is by design, and
b) There is no impairment of the user experience.
Testing Steps
1. Launch Application in target language.
2. Check text appearing in:
a) Splash/Title/Logo/Loading Screen;
b) Main Menu and all its subsidiary menus;
c) Help/Instructions Screen(s)
d) About screen;
e) Application Pause Menu and all its subsidiary menus (if present).
RESULT:
All text located in the specified areas is shown without technical display issues
that hinder legibility.
Result of Test
Pass

Annoying

39

Difficult

Impossible

Language
8.1

Correct operation

Test ID
Test Title
Warning
8.1
Language Correct operation
Test Description
Ensure that the Application works correctly with all appropriate languages.
Required for:
All applications.
Testing Note
1. Translation table with all text used in UI should be provided to Test team
before testing starts.
Testing Steps
1. If handset supports more than one language, set handset to a language not
already tested in certification testing.
2. Launch the Application and perform brief testing with aim to go through all
possible screens, menu, messages.
3. If Application Specification specifies that Application detects selected handset
language, ensure Application displays appropriate for each supported language.
4. Exit the Application
5. Repeat steps 1 to 4 for each supported language.
RESULT:
1. All text content is rendered in the correct/expected language.
2. Ensure Application detects correct language and renders content as
appropriate (if applicable).
Result of Test
Pass

Annoying

40

Difficult

Impossible

8.2

Manual selection

Test ID
Test Title
Critical
8.2
Language Manual selection
Test Description
Ensure that the Application properly allows selection of languages where
available.
Required for:
Application which allows selection of languages within the Application.
Not Required for:
Application that does not permit selection of languages within the
Application.
Testing Note
Testing Steps
1. Set Application to each language using language selection facility of the
Application.
2. Perform brief testing.
RESULT:
1. User is able to select all desired languages.
2. All text content is rendered in the correct/expected language.
Result of Test
PASS

FAIL

EXCEPTION(S)
Application does not permit selection of languages.

41

8.3

Supported formats

Test ID
Test Title
Warning
8.3
Language Supported formats
Test Description
Ensure that the Application supports all date/time/numeric/currency
features for supported languages
Required for:
All applications.
Testing Note
Testing Steps
Verify that date, time, time zone, week start, numeric separators and currency,
are formatted appropriately for the implemented languages target country and
supported throughout the Application.
RESULT:
All text content relating to date/time/numeric/currency fields are rendered in the
correct/expected language format.
Result of Test
Pass

Annoying

42

Difficult

Impossible

8.4

International characters

Test ID
Test Title
Warning
8.4
Language International characters
Test Description
Ensure that the Application accepts and displays all appropriate
international characters correctly.
Required for:
All applications.
Testing Note
Testing Steps
Verify that all data entry fields accept and properly display all International
characters for supported languages.
RESULT:
All international text characters are rendered in the correct/expected language.
Result of Test
Pass
Annoying
Difficult
Impossible

43

Performance
9.1

Suspend/resume from main menu

Test Title
Critical
Lifecycle Suspend / resume from main
menu
Test Description
Ensure that the Application suspends when at the Application main menu.
Required for:
All applications.
Testing Note
Test ID
9.1

Testing Steps
1. Launch the Application.
2. Go to the main menu of the Application.
3. Suspend the Application
4. Resume the Application
RESULT:
Application should suspend and resume correctly, and resume at a point that
does not impair the user experience.
Result of Test
PASS

44

FAIL

9.2

Suspend while executing

Test ID
Test Title
Critical
9.2
Lifecycle Suspend while executing
Test Description
Check for Suspend in the middle of Application execution.
Required for:
All applications.
Testing Note
Testing Steps
1. Launch the Application.
2. During Application execution, suspend the Application
3. Resume the Application
RESULT:
Application should suspend and resume correctly, and resume at a point that
does not impair the user experience.
Result of Test
PASS

45

FAIL

9.3

Resume

Test ID
Test Title
Critical
9.3
Lifecycle - Resume
Test Description
Ensure that the Application resumes correctly.
Required for:
All applications.
Testing Note
The objective of this test is to confirm the applications stability when suspended
and resumed multiple times from different locations in one test cycle.
Testing Steps
1. Perform Lifecycle Suspend / resume from main menu
2. Resume the Application
4. Perform Lifecycle Suspend while executing
5. Repeat step 2.
RESULT:
The Application resumes to the point where it was suspended, or to a point that
does not impair the user experience.
Result of Test
PASS

46

FAIL

9.4

Influence on terminal system features

Test Title
Critical
Lifecycle - Influence on Terminal System
Features
Test Description
Application must correctly handle situations where following user input, or
some external event (e.g. a phone call), it is switched to the background by
the terminal. Upon returning to foreground the Application must resume its
execution correctly. While in the background the Application must not emit
any audio (unless it is part of its specific purpose to do so) and all handset
functions should remain intact.
While being in the background, the Application must either not affect the
use of the system features or other Applications or, if the Application does
so, such behaviour must be described in the help file.
Not Required for:
Application which is not written to run as a Service.
Required for:
Application which is written to run as a Service.
Testing Note
1. When performing the test below, the Application either needs to be switched to
background or foreground. The actual method used depends on the functionality
of the target terminal
2. If features are found to be disabled or not able to be used and are not listed in
the help file the Application must fail this test.
3. The developer should be asked whether the Application is written to run as a
Service, and the answer should determine whether this test is applicable.
Test ID
9.4

Testing Steps
1. Launch the Application.
2. Familiarize yourself with the help file.
3. Switch Application to background while the Application is running and in each
of the following locations within the Application:
- During initial loading of the Application
- Main Menu
- In the process of normal Application usage
- In the process of loading data from the network (where applicable)
- In pause state (where applicable).
4. Try using system features and Applications of the terminal (Phone Application,
Calendar, Clock, Contacts, Browser, etc). In particular try the following:
- make a voice call
- make a video call (if supported by terminal)
- send an SMS message
- send an MMS message
- open a WAP and WEB page (if supported by terminal)
- start a streaming session using a WEB browser or media player.
5. Verify that terminals system features and Applications can still be used
normally, and where this is not the case, the Applications help file describes the
situation adequately to the user. Verify also that the Application does not emit
any audio (unless this is its specific purpose by design).
6. Switch the Application back to the foreground.
7. Verify that the Application operates normally by using it for a time period of 5
minutes.

47

Test ID
9.4

Test Title
Lifecycle - Influence on Terminal System
Features

Critical

RESULT:
1. Terminals system features and Applications can be used normally
2. In case the Application execution causes some changes to normal use of
system features and Applications, this is adequately explained in the help file of
the Application.
3. After the Application is brought back to foreground, it continues to operate
normally.
Result of Test
PASS

FAIL

EXCEPTION(S)
Application is not written to run as a Service.

48

9.5

Resource sharing - database

Test ID
Test Title
Critical
9.5
Lifecycle - Resource Sharing Database
Test Description
Check that database resources are properly shared between Application
and a competing Application.
Required for:
Applications which make use of Contacts database.
Not required for:
Applications which do not make use of Contacts database.
Testing Note
Application under test should not be the device native Contacts application.
Testing Steps
1. Launch the Application.
2. Suspend Application
3. Launch the device Contacts application
4. Add a new entry into contacts.
5. Remove an existing entry from contacts.
6. Resume the Application under test
7. Check Application state.
RESULT:
1. Application should continue from the previous state prior to being suspended.
2. Application should see the new entry and the deleted entry.
Result of Test
PASS

FAIL

Application does not use Contacts database.

49

10 Media
10.1 Application mute option
Test ID
Test Title
Warning
10.1
Media Application mute option
Test Description
Ensure that the Application has a Mute or Sound On / Off setting.
Required for:
Applications with sound settings.
Not Required for:
Application which is declared not to have a Application mute facility by
design.
Testing Note
It will be sufficient for the application to respect the settings of the device volume
controls, such that sound can be turned down to zero before the application
launches, and the application then makes no sound.
Testing Steps
Use the application and note the effects of either muting the device via the device
volume controls or via a menu setting.
RESULT:
Application must provide a means of muting background music and / or sound
effects.
Result of Test
Pass

Annoying

Difficult

Impossible

EXCEPTION(S) (Note that both Exceptions may be selected if appropriate)

Application does not have Application mute facility by design.
Application does not have any settings options.

50

10.2 Settings statuses understandable

Test ID
Test Title
Warning
10.2
Media Settings statuses understandable
Test Description
Ensure that the Application settings statuses are easily understandable.
Required for:
Applications which have Settings options.
Not required for:
Applications which do not have Settings options.
Testing Note
Testing Steps
1. Start the application.
2. Change the status of settings
RESULT:
The current status of each setting must be easily understood.
Result of Test
Pass

Annoying

Difficult

EXCEPTION(S)
Application does not have any settings options.

51

Impossible

10.3 Settings do not impair application

Test ID
Test Title
Warning
10.3
Media Settings do not impair Application
Test Description
The status of the Application settings does not impair the Application
functionality.
Required for:
Applications which have Settings options.
Not required for:
Applications which do not have Settings options.
Testing Note
Testing Steps

1. Start the application

2. Change settings
3. Observe the result.

RESULT:
The current status of the settings does not affect the Application operation (e.g.
whether or not the sound is on in a game). For example, switching off the sound
does not change the game's functionality.
Result of Test
Pass

Annoying

Difficult

EXCEPTION(S)
Application does not have any settings options.

52

Impossible

10.4 Saving settings

Test ID
Test Title
Warning
10.4
Media Saving settings
Test Description
Ensure that the Application saves all settings on exit.
Required for:
Applications which have Settings options.
Not required for:
1. Applications which do not have Settings options;
2. Applications which do not save changes to Settings by design.
Testing Note
Testing Steps

1.
2.
3.
4.

Start the application

Change an item in settings
Exit and restart the application
Observe the setting status

RESULT:
When an Application exits, all settings must be saved.
Restarting the Application will restore the saved settings.
Result of Test
Pass

Annoying

Difficult

Impossible

EXCEPTION(S)
Application does not have any settings options.
Application is declared not to save settings on close by design.

53

10.5 Specific functions

Test ID
Test Title
Warning
10.5
Media Specific functions
Test Description
Ensure Application sounds have specific functions and should not be over
utilised.
Required for:
Applications with sound.
Not required for:
Applications without sound.
Testing Note
Testing Steps
Use the application and observe the sounds utilised
RESULT:
Each sound should have a specific function, and should not be over used (e.g.
game completing with a minute of random noise is not permitted).
Result of Test
Pass

Annoying

Difficult

EXCEPTION(S)
Application does not have any sounds.

54

Impossible

11 Menu
11.1 Help and about
Test ID
Test Title
Warning
11.1
Menu Structure Help & About items
Test Description
The Application should contain standard Menu items Help & About.
Required for:
Applications with user interface capable of displaying information to user.
Not required for:
Applications without user interface capable of displaying information to
user.
Testing Note 1
It is a requirement that applications with a user interface should contain Help
information, to explain to the user how the Application works; and About
information, so that the user can easily identify the exact version of the
Application installed, the developer of the Application, and the developer contact
details.
Testing Note 2
This test can be passed if the application contains the information in Testing Note
1 and it is easy to access, even if the items are not named exactly as in the test
steps. The tester should indicate in their report if the application has passed this
test on a value judgement like this, rather than a literal interpretation of the test
steps.
Testing Note 3
If it is clear that the applications purpose requires network coverage to operate,
then it will be sufficient for the Help to be provided through a browser connection
rather than being contained in the application. In the opposite case, where most
functions of the application can be used while the device is offline, then the
application should have Help that can be accessed without needing a data
connection.
Testing Note 4
Where the amount or type of Help information appears insufficient for easy use of
the application, the tester should give specific instances in their report.
Testing Steps

1. Start the application

2. Access the Help and About sections

RESULT:
1. Menu items like Help and About are required to be presented on the main
menu or other easily-found screen of the Application.
About functions should contain the Application version number and author
information.
2. Help should include the aim of the Application, usage of the keys (e.g. for
games) and other instructions. If the text of the help is too long, it should be
divided into smaller sections and/or organized differently.
3. Help must be accurate and consistent with the Application functionality and the
handset specifics.

55

Test ID
Test Title
11.1
Menu Structure Help & About items
Result of Test
Annoying

Difficult

Warning
continued
from previous page

Impossible

EXCEPTION(S)
Application has no user menu by design, or the application design / purpose is
such that these items cannot be displayed to the user.

56

11.2 Valid actions

Test ID
Test Title
Critical
11.2
Menu Options Valid actions
Test Description
Selected and/or changed Application items should invoke valid actions.
Required for:
All applications.
Testing Note
Testing Steps

1. Start and use application.

2. Observe the results.

RESULT:
All Application items that can be selected and/or changed by user, must invoke
valid actions according with the Application Specifications
Result of Test
PASS

57

FAIL

12 Functionality
12.1 Functionality sanity check
Test ID
Test Title
12.1
Major Functionality Sanity check
Test Description
Major Functionality Sanity Check.
Required for:
All applications.
Testing Note

Critical

Testing Steps
1. Launch the Application.
2. Operate the Application, exploring all screens and functions.
3. Document all instances of non-compliance with Application specifications.
4. Document unexpected functionality outside scope of Application specifications.
RESULT:
All specific Application functionality such as algorithms, calculations,
measurements, scoring, etc. must be implemented correctly.
Result of Test
PASS

58

FAIL

12.2 Application hidden features

Test Title
Critical
Major Functionality Application hidden
features
Test Description
The Application does not introduce any hidden features, its functionality
set is consistent with the help and it does not harm the data on the device.
Required for:
All applications.
Testing Note
1. The tester will perform the test as specified above, but the developer must
ensure that this requirement is fulfilled throughout the Application.
2. Allowable functions are:
Cheat codes
Unlocking the Application, for example from demo version to a full
version.
3. The application must not use any public storage such as the gallery for
images( or sounds or similar resources) without informing the user beforehand.
Test ID
12.2

Testing Steps
1. Install users personal data to the device (for example calendar, contact, to-do,
images, text files, documents, etc).
2. Launch the Application.
3. Familiarise yourself with the help file.
4. Use the Application and all of its features for a time period of 15 minutes.
5. Compare the documented Application functionality to the features you find,
and what is in the help file.
RESULT:
1. All the features are introduced in the Help, the Application has no hidden
features.
2. The data inserted to the device has not been corrupted.
3. The phone bill (or log) does not show any additional communication.
4. The phone bill (or log or data counter, if applicable) does not show an
excessive amount of transferred data.
5. The other Applications in the device must run as they did before Application
installation.
Result of Test
PASS

59

FAIL

13 Keys
13.1 Scrolling in menus
Test ID
Test Title
13.1
Scrolling in menus
Test Description
Scrolling in menus.
Required for:
Applications with user interaction.
Not required for:
Applications without user interaction.
Testing Note

Critical

Testing Steps
1. Launch the Application.
2. Use the keypad or other navigation device to scroll vertically and (if applicable)
horizontally in the Main menu item list.
RESULT:
This MUST scroll in the menu item list with no adverse effects on the
Application.
Result of Test
PASS

FAIL

EXCEPTION(S)
Application does not have user interaction by design.

60

13.2 Text field scrolling

Test ID
Test Title
Warning
13.2
Text field scrolling
Test Description
Scrolling in text fields and About / Help screens.
Required for:
Applications with user interaction.
Not required for:
Applications without user interaction.
Testing Note
Testing Steps
1. Launch the Application.
2. Use the scrolling functions of the keypad or other navigation device in a text
dialog, for example: About and Help.
RESULT:
This should scroll vertically and (if applicable) horizontally in the dialog.
Result of Test
Pass

Annoying

Difficult

Impossible

EXCEPTION(S)
Application does not have user interaction by design.

61

13.3 Pause
Test ID
Test Title
Critical
13.3
Pause
Test Description
The Application must support a pause feature in areas of the Application
where immediate user interaction is needed (for example in game).
The pause feature must support an option to resume the Application, and
an option to go back to the main menu of the Application.
Required for:
Applications requiring time-sensitive user interaction.
Not Required for:
1. Applications where immediate user intervention is not needed (for
example timer Application);
2. Applications without user interaction.
Testing Note
The developer is encouraged to use the available APIs for pause and continue
methods.
Testing Steps
1. Launch the Application.
2. Use the Application and its features.
3. Check that the user can pause the Application at any time if so desired.
4. Check that the Application can also be "un-paused".
RESULT:
1. The user can pause the Application and the pause feature must support an
option to resume .
2. All time-specific features of the Application are disabled at the time of the
pause.
3. There is a clear indication that the Application is in a paused state.
4. There is a clear indication how the user can return from the paused state.
Result of Test
PASS

FAIL

EXCEPTION(S)
Application does not require immediate user intervention.
Application does not have user interaction by design.

62

13.4 Simultaneous key presses or multiple touch

Test Title
Critical
Simultaneous key presses or multiple
touch
Test Description
Ensure that the Application copes with simultaneous key presses or
multiple touch
Required for:
Applications with user interaction.
Not required for:
Applications without user interaction.
Testing Note
Test ID
13.4

Testing Steps
1. Launch the Application.
2. Press combinations of keys simultaneously, from a selection of UP, DOWN,
LEFT, RIGHT, CENTER and all other available keys or use multiple touch
combinations. Do not use any which intentionally terminate or exit the
application, or intentionally launch a function that would invalidate the test.
RESULT:
The Application should not be put into an unusable or incomprehensible state by
simultaneous key presses or multiple touches. Any error messages generated
should be meaningful.
Result of Test
PASS

FAIL

EXCEPTION(S)
Application does not have user interaction by design.

63

13.5 Multi key presses or multi touch

Test ID
Test Title
Critical
13.6
Multi key presses or multi touch
Test Description
If device and application support multi key press operation, these should
perform as expected.
Required for:
Application that supports multi key press or multi touch actions, on device
that also supports this.
Not required for:
Application or device without support for multi key press or multi touch
Testing Note
Testing Steps
1. Launch the Application.
2. Use the multi key press or multi touch actions as documented by the
developer in the Help, or documented separately.
RESULT:
All reactions to multi key presses or multi touch should be as predicted by the
documentation and should not leave the Application in an unusable state.
Result of Test
PASS

FAIL

EXCEPTION(S)
Application does not have user interaction by design.
Application does not support multi key press or multi touch
Device does not support multi key press or multi touch

64

14 Device Specific Tests

14.1 Device close
Test ID
Test Title
Critical
14.1
Action - Device Close
Test Description
Ensure that the Application while launching handles closing of the device
correctly.
Required for:
Applications on devices with open / close functionality.
Not Required for:
Device without open / close functionality.
Testing Note
Testing Steps
1. Launch the Application.
2. While the Application is launching (i.e. "Please wait screen), close the device
and then 3-4 times quickly open and close it.
3. Open the device.
RESULT:
The Application returns to the same state before the interruption.
Result of Test
PASS

FAIL

EXCEPTION(S)
Device does not have open / close functionality.

65

14.2 Device open

Test ID
Test Title
Critical
14.2
Action Device Open
Test Description
Ensure that the Application handles device opening correctly.
Required for:
Applications on devices with open / close functionality.
Not Required for:
Device without open / close functionality.
Testing Note
Testing Steps
1. Launch the Application.
2. Use the Application and its features.
3. Close the device.
4. Open the device.
RESULT:
The Application returns to the same state before the interruption.
Result of Test
PASS

FAIL

EXCEPTION(S)
Device does not have open / close functionality.

66

15 Stability
15.1 Application stability
Test ID
Test Title
Critical (if reproducible)
15.1
Stability Application stability
Test Description
The Application must not crash or freeze at any time while running on the
device.
Required for:
All applications.
Testing Note
1. During any time of the testing observe the Application behaviour.
2. The report must indicate if the error can be reproduced or not, and the steps to
do so
Testing Steps
1. Start to test the Application.
2. Observe the Application behaviour during the testing.
RESULT:
The Application must not freeze or exit unexpectedly at any time.
Result of Test
PASS

67

FAIL

15.2 Application behaviour after forced close

Test Title
Critical
Stability Application behaviour after
forcible close by System
Test Description
Application must preserve sufficient state information to cope with forcible
close by the system.
Required for:
All applications.
Testing Note
If it is not possible to remove the device battery, a power cycle should be forced
with the device power key instead.
Testing Steps
1. Start the Application.
2. Exercise the functionality of the application, including any function that builds
or saves information.
3. Press the Home key to return to the Home screen and ensure the application
is switched into a paused state.
4. Remove the battery to instantly kill the application, as the system does when
dealing with a low memory situation.
5. Restart the handset and open the application again.
6. Check the application is in a usable state and any information built or saved
before the close has been retained.
Test ID
15.2

RESULT:
The Application must not lose any information that it implies would be preserved,
nor become difficult to use subsequently, as a result of a forcible closure by the
system.
Result of Test
PASS

68

FAIL

16 Data Handling
16.1 Save game state
Test ID
Test Title
Critical
16.1
Save record Game state
Test Description
Ensure that the Application can save its game state/high score table
information into persistent memory.
Required for:
1. Application where user may exit part completed game;
2. Application where a player high score value is identified.
Not Required for:
Application which does not have game state / high score elements.
Testing Note
Testing Steps
1. Launch the Application and start a game.
2. Bring up the game menu and exit saving game position.
3. Run Application again and continue game.
4. Play game until a high score is obtained.
5. Bring up game menu and check High score table.
6. Exit Application and restart.
7. Check high score table.
RESULT:
1. Game state should be as was immediately prior to Application exit.
2. The high score table should represent the scores recorded during the
Application test.
Result of Test
PASS

FAIL

EXCEPTION(S)
Application does not have game state or high score elements.

69

16.2 Data deletion

Test ID
Test Title
Critical
16.2
Delete Data deletion
Test Description
The Application must indicate whether data will be permanently deleted or
offer easy reversal of the deletion.
Required for:
Application which has function to delete data.
Not required for:
Application which does not have function to delete data.
Testing Note
The user should always be required to confirm deletion of data, or have an option
to undo deletion, to reduce risk of accidental loss of information through user
error.
Testing Steps
1. Launch the Application.
2. Use the function which deletes something on the Application.
3. Check if there is a reversal (undo) available for the user or that the user is
notified before deletion is permanent.
RESULT:
1. Before the data deletion, the Application notified the user of deletion, or the
Application has an undo feature.
2. If undo is present it works as expected.
Result of Test
PASS

FAIL

EXCEPTION(S)
Application does not have function to delete data.

70

16.3 Modify record

Test ID
Test Title
Critical
16.3
Modify Record
Test Description
Ensure that the Application can modify its game state/high score table
information into persistent memory.
Required for:
1. Application which may be exited part-way through game play;
2. Application which identifies a user high score value.
Not Required for:
Application which does not have game state / high score elements.
Testing Note
Repeating the save of game state and high score ensures that the values initially
saved can be updated.
Testing Steps
Repeat Save record Game state
RESULT:
Game state is saved/updated
Result of Test
PASS

FAIL

EXCEPTION(S)
Application does not have game state / high score elements.

71

17 Security
17.1 Encryption
Test ID
Test Title
Critical
17.1
Security Encryption
Test Description
When connections are used encryption is used for sending / receiving
sensitive data.
Required for:
Application identified as communicating sensitive data.
Not Required for:
Application identified as not communicating sensitive data.
Testing Note
All sensitive information (personal data, credit card & banking information etc.)
must be encrypted during transmission over any network or communication link.
Testing Steps
Refer to supplied information about the application. If the application transmits
sensitive data and the developer has not stated encryption is used, this test
cannot be passed. The manifest should be checked for an https permission
request which will indicate that secure, encrypted transmission is used.
RESULT:
It has been declared that the Application uses encryption when communicating
sensitive data.
Result of Test
PASS

FAIL

EXCEPTION(S)
Application is stated not to communicate sensitive data.

72

17.2 Passwords
Test ID
Test Title
Critical
17.2
Security Passwords
Test Description
Passwords or other sensitive data are not stored in the device and are not
echoed when entered into the Application, sensitive data is always
protected by password.
Required for:
Application which uses passwords or other sensitive data.
Not Required for:
Application which does not use passwords or other sensitive data.
Testing Note
1. With passwords the desired approach is that the Application shows which
character the user selected and then changes that to an asterisk (*).
2. If the user is explicitly asked for permission, a password can be stored to the
device memory.
3. The objective of the test is to minimise the risk of access to sensitive
information should the device be lost, by ensuring that no authentication data
can be re-used by simply re-opening the application
4. Once sensitive data has been entered, it should not be displayed in plain text
anywhere in the application, however it is allowable to have no more than
25% of a sensitive value displayed in plain text (e.g. 4 of the 16 digits of a
card number) where this assists the user to distinguish between multiple
cards or accounts.
5. For the purpose of this test, personal contact details such as those recorded
in the phonebook should not be regarded as sensitive. Bank / credit card
account numbers, balances & access codes or passwords should be treated
as sensitive and be protected from unrestricted access.
Testing Steps
1. Launch the Application.
2. Go to the section where passwords or other sensitive data (such as credit card
details) is input or displayed.
3. Input or read some sensitive data. Observe how the data are displayed on the
screen.
4. Exit the Application.
5. Launch the Application.
6. Go to the place where sensitive data was inserted or read.
7. See if the data is still visible, or can be redisplayed without requiring a
password at any point.
RESULT:
1. Entering a password or other sensitive data will not leave it in clear text if
completion of the fields is interrupted but not exited.
2. Passwords, credit card details, or other sensitive data do not remain in clear
text in the fields where they were previously entered, when the application is reentered.
3. Sensitive personal data should always need entry of a password before it can
be accessed.

73

continued from previous page

Test ID
Test Title
17.2
Security Passwords
Result of Test
PASS

Critical

FAIL

EXCEPTION(S)
Application does not use passwords or other sensitive data.

74

Version control
Version
V1.0
V1.1

Date
March 2011
June 2012

Changes made
n/a
General changes made:
Added critical tests and warning test levels
Included Simple App Testing sub-set
Included Smoke Test sub-set
Included Framework App Testing sub-set
Added more testing notes for testers
Tests removed:
Invalid Web Access Set-up
Settings Combination
Selection Key
Tests added:
Network connectivity: resource downloading
Tests combined:
Memory card insertion and memory card insertion & removal

DISCLAIMER. THIS UNIFIED TESTING CRITERIA DOCUMENT ("DOCUMENT") IS FOR INFORMATIONAL

PURPOSES ONLY. YOUR USE OF THIS DOCUMENT AND THE INFORMATION PROVIDED HEREIN IS AT
YOUR OWN RISK. THE DOCUMENT IS PROVIDED ON AN "AS IS" AND "WITH ALL FAULTS" BASIS. THE
UNIFIED TESTING INTITIATIVE INCLUDING THE MEMBERS IT IS COMPRISED THEREOF DISCLAIM ALL
EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS, AND WARRANTIES OF ANY KIND, INCLUDING
ANY IMPLIED WARRANTY OR CONDITION OF MERCHANTABILITY, SATISFACTORY QUALITY, FITNESS
FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. THE UNIFIED TESTING INITIATIVE INCLUDING
THE MEMBERS IT IS COMPRISED THEREOF MAKE NO REPRESENTATIONS, WARRANTIES, CONDITIONS OR
GUARANTEES AS TO THE USEFULNESS, QUALITY, SUITABILITY, TRUTH, ACCURACY OR COMPLETENESS
OF THIS DOCUMENT AND MAY CHANGE THIS DOCUMENT AT ANY TIME WITHOUT NOTICE.

75