TRUE BREW Test Procedures

S Test
S R App.
t Notes, Motivation, and Expected Results. Result Test Results
e e Category Test Requirement and Procedures Spec. P/F/D
e Observations, Issues, and Comments
c q Ref N
p

3.1 0 Entrance Criteria

3.1 1 0 Test Name: Developer Signature NA N/A
Note: This test is not performed by developer. Developer
MOD and MIF shall be signed. All signed files must be signed
should ensure MOD and MIF are signed (mandatory) and
3.1 1 0 Requirement: with valid developer signature. Files that are modified on the
others are signed as appropriate. Files submitted for Carrier
handset must be unsigned or signed-modifiable.
Managed testing may not be signed by developer.
3.1 2 0 Test Name: MIF Graphics NA N/A
MIF graphics (image, thumbnail, and icon) are the correct size.
It must be possible to visually determine that a graphic has
been selected in the Application Manager. The sizes are as
follows: thumbnail 16 (w) x 16 (h) pixels; icon image 26 (w) x
3.1 2 0 Requirement: N/A
26 (h) pixels; image icon (for BREW 2.0 and beyond) 65 (w) x
42 (h) pixels or smaller. For earlier BREW versions, the image
icon is less than or equal to the maximum size specified in
device data sheet.
Use the BREW MIF Editor to extract each image using the
3.1 2 1 Procedure: Extract option. Save the image file for each of the following Result: Images exist on PC disk.
fields:; "Icon" file; "Thumbnail" file; "Image" file;
Open the image (saved as a file) in Paint (or similar tool), press Result: Dimension of each graphic (image, icon, thumbnail)
3.1 2 2 Procedure:
CTRL+E (in Paint) to view the size of the graphic. satisfy test requirement.
Open the image (saved as a file) in Paint (or similar tool),
Result: Color depth of images satisfies handset requirements
3.1 2 3 Procedure: select File Save As (in Paint) to view the number of colors in
(DDS) (color depth does not exceed that of handset).
the bit map. Do not save the file.
Result: Tester can visually verify that AUT has been selected
3.1 2 4 Procedure: On handset, select application using App Manager.
(border around graphic).
Motivation: Handset may allow user to configure view (icon,
thumbnail, etc). Ensure by visible inspection that graphic for
3.1 2 5 Procedure: Repeat step 4 for each application view supported by handset. AUT is highlighted when selected in each view. Result:
Tester can visually verify that AUT has been selected (border
around graphic).
3.1 3 0 Test Name: MIF Settings NA N/A
The AUT’s ClassID is not displayed as a dependency. The MIF
does not define both an application and an extension. The MIF
files does not have the "hidden" flag checked for any applet.
3.1 3 0 Requirement: N/A
All notifications, privileges, and protected classes used by the
AUT are documented in the App. Spec. The Screensaver box
is only selected for screen-saver AUTs.
Result: MIF contents appear without error. Note: This test
3.1 3 1 Procedure: Open the MIF with the MIF Editor. must be performed on the MIF in submitted package. Cannot
be performed on MIF pulled off handset.
Under the Applets tab, view the ClassID(s) of under Applet Motivation: A Class ID cannot be declared as an Applet and a
3.1 3 2 Procedure: Information. Under the Dependencies tab, view the Class IDs Dependency. Result: ClassIDs listed under Applets section
of the "Used" dependencies. are not repeated in the Dependencies "Used" section.
Motivation: A Class ID cannot be declared asn an Applet and
Select the Extensions Tab. View the "Exported Classes" Class
3.1 3 3 Procedure: an Extension. Result: Class IDs listed under Applets section
IDs referenced under the Extensions tab.
are not repeated in the Extensions tab.
Under the General tab, review the privilege level settings
Motivation: Developers must justify use of privileges. Result:
3.1 3 4 Procedure: selected in the MIF against those documented in the App
Each selected privilege is documented in the App Spec.
Spec.
Select the Advanced button and review the privilege level Result: None of these privilege levels are checked. Note:
3.1 3 5 Procedure:
settings. These privileges are reserved.
Motivation: Developer must justify use of notifications in App
3.1 3 6 Procedure: From the Applets tab, select Advanced. View the notifications. Spec. Result: All notifications appearing in the MIF
Notifications field are described in the App Spec.

1
QUALCOMM Proprietary 80-D4187-3 Rev.A
 TRUE BREW Test Procedures
From the Applets tab, view the String Format. Compare with
3.1 3 7 Procedure: the "encoding" field supported by the handset as specified in Result: Mobile handset supports specified String Format.
the "Font Configuration" section of the DDS.
Result: The Screen-saver box is selected. Note: App Spec
If this is a screen-saver application: From the Applets tab,
3.1 3 8 Procedure: "Application Goal and Purpose" field should describe
select Advanced. View the Settings.
application as a screen saver.
Under the Dependencies tab, view the Class ID of all external
Result: All references to external Class IDs are documented
3.1 3 9 Procedure: classes used by the application ("Used" field). Compare these
in the App Spec. Developer justifies use of external classes.
Class IDs with those documented in the App Spec.
3.1 4 0 Test Name: Nested Directories in Package NA N/A
The directory containing an ARM MOD file has no
3.1 4 0 Requirement: subdirectories. Each ARM MOD file of a multi-module N/A
application has a separate directory.
Result: There are no nested directories within the AUT's
3.1 4 1 Procedure: View the AUT's directory structure.
directory.
3.1 5 0 Test Name: Zero Byte Files in Package NA N/A
The AUT ARM directory does not contain any empty files (size
3.1 5 0 Requirement: N/A
0 bytes).
3.1 5 1 Procedure: Review the size of all files in the ARM directory. Result: Every file is at least one byte in size.
3.1 6 0 Test Name: Download, Startup, Delete NA N/A
The AUT can be downloaded from the ADS. The AUT appears
in the Application Manager. The AUT can be started from the
Application Manager. The AUT can be deleted from the
3.1 6 0 Requirement: Application Manager. All modules created on the handset N/A
during application download are removed when the application
is removed, including extensions (with the exception of
extensions referenced by other applications).
3.1 6 1 Procedure: Start Mobile Shop and select AUT for download. Result: AUT downloads onto handset.
3.1 6 2 Procedure: Select "Yes" when asked whether AUT should be started. Result: AUT starts without error.
3.1 6 3 Procedure: Exit the AUT. Result: Returns to Application Manager.
From Application Manager (BREW Main Screen), select Icon
3.1 6 4 Procedure: Result: AUT starts without error.
for AUT
Result: Returns to Application Manager (BREW Main
3.1 6 5 Procedure: Exit the AUT.
Screen).
On BREW 1.x handsets start Mobile Shop, select Options. On
3.1 6 6 Procedure: Result: AUT name appears
BREW 2.x handsets, select Settings, then Manage Apps.
Result: Deletion succeeds. On BREW 1.x, AUT no longer
3.1 6 7 Procedure: Select AUT, then select Remove. appears in Options screen. On BREW 2.x, app no longer
appears in Manage Apps screen.
Result: (1) Verify absence of files using App Loader; (2) Use
3.1 6 8 Procedure: Ensure AUT removed. App Loader to verify absence of referenced extensions. (3)
Verify app no longer appears in App Manager.
3.1 7 0 Test Name: Version Number 1 N/A
The App. Spec. documents the software version of the AUT.
The version in the App. Spec. matches the version that is
either (a) contained in the MIF or (b) embedded/compiled into
the AUT (as specified in the App. Spec.). These version
3.1 7 0 Requirement: numbers must match exactly. It must be possible to N/A
unambiguously associated an application that is on the
handset with the particular submission and Application
Specification. The software version number must increase with
each new submission of the AUT.
3.1 7 1 Procedure: Review App. Spec. Result: App. Spec. contains AUT version number.
View AUT version number on handset. Compare with version Result: AUT on handset contains at least one version number
number specified in App Spec. See "Viewing application that end user can read. All version numbers match that in App
3.1 7 2 Procedure:
version" in Appendix B of Test Guide to determine how to view Spec so AUT is uniquely identified and uniquely associated
AUT version number on handset. with submission.
Note: Record for archival and reference. Used "D" for Test
3.1 7 3 Procedure: Record application name
Result.
Note: Record for archival and reference. Used "D" for Test
3.1 7 4 Procedure: Record application version
Result.

2
QUALCOMM Proprietary 80-D4187-3 Rev.A
 TRUE BREW Test Procedures
Note: Record for archival and reference. Used "D" for Test
3.1 7 5 Procedure: Record handset model
Result
Note: Record for archival and reference. Used "D" for Test
3.1 7 6 Procedure: Record handset S/W version
Result
3.1 8 0 Test Name: Developer Test Results 1 N/A
The application submission includes a filled out copy of the test
cases as documented in Appendix A. For each requirement,
the developer has specified whether the application meets the
3.1 8 0 Requirement:
requirements (P), does not meet the requirement (F), or the
requirement does not apply (NA). Notes are included as
appropriate.
Result: AUT passes all applicable tests or has notes
3.1 8 1 Procedure: Review test results submitted with application submission. indicating extenuating reasons for failure of one or more test
case.

3.2 0 Exploratory Testing

3.2 1 0 Test Name: Primary Functionality 3, 4 N/A
The AUT functions as specified in the App. Spec. The AUT
3.2 1 0 Requirement: does not contain functionality that does not fall within the scope N/A
of the functionality described in the App. Spec.
Result: AUT operates according to App. Spec. Note: When
Operate AUT. Explore all screens and functions. Document
performing exploratory, the tester should keep in mind the
3.2 1 1 Procedure: all instances of non-compliance with App. Spec. Document
specific tests in the rest of the tes guide. This will speed the
unexpected functionality outside scope of App. Spec.
execution of these tests when they are performed.
Examine AUT directory and shared directory. Document in the Note: AUT does not pass or fail on the results of this
3.2 1 2 Procedure: test report the number and sizes of files created in AUT observation. Data will be made available to operators through
directories and BREW Shared Directory. test report.
3.2 2 0 Test Name: User Interface 3, 4 N/A
The AUT primary functionality can be operated through the
user interface provided by the AUT. Issues will be noted in the
3.2 2 0 Requirement: N/A
following areas: Drawing screens, Screen contents, Keypad
input, Text entry, Scroll bars.
Operate AUT. Explore all screens and functions, paying User interface has no problems with Drawing Screens, display
3.2 2 1 Procedure:
particular attention to the presentation of text, graphics, etc. of screen contents, keypad input, text entry, or scroll bars.
3.2 3 0 Test Name: Supported Languages 1 N/A
The AUT functions as specified in the App. Spec. for each
3.2 3 0 Requirement: N/A
language supported by the AUT.
If handset supports more than one language, set handset to a
3.2 3 1 Procedure: Language on OEM interface changes to selected langauage.
language not already tested in exploratory testing.
Start AUT and perform exploratory testing. If App Spec Result: AUT operates with handset configured to new
specifies that AUT detects selected handset language, ensure language. AUT displays selected language if AUT supports
3.2 3 2 Procedure:
AUT displays appropriate for each support language specified that language and AUT automatically displays languaged
in App Spec. Exit AUT. selected on handset.
3.2 3 3 Procedure: Repeat Steps 1-2 for each supported language. As stated above.
If AUT allows selection of language through AUT menu, set
3.2 3 4 Procedure: AUT to each language as specified in App Spec. Perform Application displays each selected language.
exploratory.
3.2 4 0 Test Name: Content Server 14 N/A
The AUT functions properly on a sampling of data that resides
3.2 4 0 Requirement: N/A
on the content server.
If AUT accesses a content server, visit each screen that
accesses the content server. For each screen that accesses
3.2 4 1 Procedure: content server, retrieve sampling of content (trying to achieve Content can be retrieved and displayed or used by the AUT.
full-coverage of content types--not full coverage of all instances
of content).

3.3 0 Handset/AUT Interaction

3.3 1 0 Test Name: Suspend/Resume 9 N/A

3
QUALCOMM Proprietary 80-D4187-3 Rev.A
 TRUE BREW Test Procedures
The AUT suspends, maintaining significant AUT state (for
example, it doesn't lose data entered by the user), and it
resumes at or near the point of suspension. Suspend can
3.3 1 0 Requirement: occur because of incoming voice calls, incoming SMS, and N/A
alerts (including the startup of a native or BREW screen-
saver). The AUT does not interfere with the ability to read the
OEM Caller ID display.
Note: It is not necessary to evaluate voice quality during any
3.3 1 1 Procedure: Call the handset while the AUT is on the main screen. tests involving voice calls. Result: AUT suspends. Caller ID
display visible.
3.3 1 2 Procedure: Answer call. Result: AUT remains suspended.
Result: AUT suspends, caller ID screen visible, and AUT then
3.3 1 3 Procedure: End call from AUT.
resumes back to AUT main screen.
Repeat steps 1 through 3, this time ending call from calling Result: AUT suspends, caller ID screen visible, and AUT then
3.3 1 4 Procedure:
side. resumes back to main screen.
Result: AUT suspends, caller ID screen visible, and AUT then
3.3 1 5 Procedure: Repeat steps 1 through 3, this time refusing call on handset.
resumes back to main screen.
If AUT is a networking application operating on a CDMA 1X Motivation: A dormant data connection may suspend when
network, repeat steps 1 through 3 while data connection is receiving an incoming voice call. Result: AUT suspend, call
3.3 1 6 Procedure:
dormant. And resume, transfer data across data connection ID screen sivible, and AUT then resumes back to main screen.
(e.g. download ringtone). Data transfer succeeds.
If handset support other means of generating suspend events
(e.g. side volume control, attachment/removal of power chord), Result: AUT suspends, caller ID screen visible, and AUT then
3.3 1 7 Procedure:
generate suspend events using this means while on AUT main resumes back to main screen.
screen.
Result: AUT suspends, native SMS display visible, and AUT
Generate periodic SMS event (e.g. every 10 seconds). Repeat
3.3 1 8 Procedure: then resumes back to or near point of suspension. Significant
exploratory testing in the presence of regular suspend event.
data not lost.
Result: AUT suspends, native SMS display visible, and AUT
3.3 1 9 Procedure: Repeat step 8, focusing in on AUT startup and exit then resumes back to or near point of suspension. Significant
data not lost.
Result: AUT suspends, native SMS display visible, and AUT
then resumes back to or near point of suspension. Significant
Repeat step 8, focusing on data call setup, activity (data data not lost. Data connection may be lost on many handsets.
3.3 1 10 Procedure:
transfer) and idle/dormant time periods. Network apps only. It is not a requirement that the AUT re-establish the data
connection if it is lost (though certainly a user-friendly
behavior).
3.3 2 0 Test Name: Handset Core Features Unaffected by AUT NA N/A
Handset Core Features Unaffected by AUT: Operation of the
AUT does not interfere with core handset functionality. After
executing and terminating an application, the following handset
3.3 2 0 Requirement: N/A
features are functioning: (1) incoming voice call, (2) incoming
SMS; (3) outgoing voice call; (4) outgoing SMS; (5) data calls
end within linger timeout value (networking applications only).
3.3 2 1 Procedure: Start AUT, perform limited exploratory testing, exit AUT. Result: AUT operates according to App. Spec.
3.3 2 2 Procedure: Initiate, establish, and end outgoing call from handset. Result: Successful call.
3.3 2 3 Procedure: Initiate, establish, and end incoming call to handset. Result: Successful call.
3.3 2 4 Procedure: Send SMS from handset. Result: Successful SMS from handset.
3.3 2 5 Procedure: Send SMS to handset. Result: Successful SMS to handset.
3.4 0 BREW Features
3.4 1 0 Test Name: Licensing 6 N/A
For an AUT supporting usage-based License Type (Price Type
either Purchase or Demo), ensure that the remaining number
of uses is decremented according to the rules specified in the
3.4 1 0 Requirement: N/A
App. Spec. For an AUT that restricts AUT functionality for the
Demo Price Type, ensure that restricted functionality cannot be
invoked with Demo Price Type.

4
QUALCOMM Proprietary 80-D4187-3 Rev.A
 TRUE BREW Test Procedures
Download AUT from test server by purchasing licenses (e.g. 3
Result: AUT resides on handset with purchased number of
3.4 1 1 Procedure: licenses). Developer can add uses to the MIF using the MIF
uses.
Editor. Note Price Type is Purchase, License Type is Uses.
Start the AUT. Note number of Uses. Operate to expire a
single use (as specified in the App Spec). This may require Result: License increments or decrements at correct logical
3.4 1 2 Procedure:
terminating and restarting the AUT. Observe number of uses points per App Spec.
left.
3.4 1 3 Procedure: Repeat step 2 until all uses expired. Result: License expires at appropriate value (per App Spec).
3.4 1 4 Procedure: StartAUT, attempt to use when license expired. Result: AUT informs user that uses are depleted.
Download AUT from test server with unlimited license
3.4 1 5 Procedure: Result: AUT resides on handset with unlimited uses.
(developer creates condition using MIF Editor).
Result: AUTs supporting unlimited (per App Spec) operate
3.4 1 6 Procedure: Start AUT. Note number of uses. Operate AUT. without expiring. AUTs not supporting unlimited notify user
and either terminate or allow user to terminate.
Repeat steps 1 through 5 for AUTs supporting Demo Price Result: AUT supports Demo Purchase Type as specified in
3.4 1 7 Procedure:
Type and Uses License type. the App Spec.
3.4 2 0 Test Name: Networking 14 N/A
The AUT establishes, maintains, and tears down a data call for
each network protocol supported by the handset (for example,
IS-95B, CDMA2000 1X, GPRS). After exiting the application
3.4 2 0 Requirement: N/A
(through any means), the data call ends within the linger
timeout value (per device data sheet). This is applicable only to
applications supporting this capability.
Download AUT over network under test (developers cable
3.4 2 1 Procedure: load). Goal is to ensure download succeeds on particular AUT downloads onto handset.
network.
3.4 2 2 Procedure: Operate AUT. Initiate a data call. Result: Data call is established. Data transfer succeeds.
Motivation: Ensure data transfer succeeds before data call
Immediately initiate another data call using the same screen or has had a chance to close or go idle (unless AUT closes
3.4 2 3 Procedure:
feature in Step 2. connection immediately after use). Result: Data transfer
succeeds.
Result: Data call icon drops, showing that the data call has
3.4 2 4 Procedure: Exit AUT. Ensure data call drops within linger timer.
terminated.
Repeat Steps 2-4 for each AUT screen or feature that uses
3.4 2 5 Procedure: Result: Data transfers succeed.
data services.
3.4 2 6 Procedure: Exit the AUT and Application Manager. Return to native OEM screen.
Motivation: ensure use of data services does not affect OEM
3.4 2 7 Procedure: Initiate, establish, and terminate a voice call from the handset.
voice services. Result: Voice call succeeds.
Motivation: (1) Ensure no problems when END occurs during
Start AUT. Initiate data call. Terminate AUT using END key
call setup; (2) Ensure AUT resets linger time if modified by
3.4 2 8 Procedure: while initiating data call. Ensure Data call drops within linger
AUT. Result: AUT exist. Return to native OEM screen. Data
timer.
call drops after linger timeout.
Motivation: Ensure AUT can re-establish connection. Result:
3.4 2 9 Procedure: Restart AUT. Initiate data call from same screen in Step 8.
Data connection established. Data transferred.
Motivation: (1) Ensure no problems when END occurs during
Repeat Steps 8-9 with modification that AUT is terminated with
data transfers (2) Ensure AUT resets linger time if modified by
3.4 2 10 Procedure: END key while data is transferring over the data call. Ensure
AUT. Data connection re-established. Data call drops within
data call drops within linger timer.
linger timer after END.
Repeat Steps 8-10 for each AUT screen or feature that uses Result: Data connection re-established. Data call drops within
3.4 2 11 Procedure:
data services. linger timer after END.
Motivation: Ensure no problems when connection is either (1)
Start AUT. Initiate data call. Allow AUT to sit idle for longer
torn down by application because idle or (2) connection goes
3.4 2 12 Procedure: than linger timer (wait linger timer plus 15 seconds). Initiate
dormant because of 1X dormancy.Result: Data transfers
another data call from same screen.
across idle/dormant connection succeeds.
Repeat step 12 for all AUT screens or functions that initiate Result: Data transfers across idle/dormant connection
3.4 2 13 Procedure:
data calls. succeeds.

5
QUALCOMM Proprietary 80-D4187-3 Rev.A
 TRUE BREW Test Procedures
Repeat steps 1-13 for each network protocol supported by the
handset (e.g. IS-95B, CDMA 2000 1X, GPRS, CDMA EVDO). Result: Data connections established. Data transferred
3.4 2 14 Procedure:
This may require configuring the handset and/or operating with successfully.
a different OEM S/W build.
3.4 3 0 Test Name: Voice Calls 13 N/A
The AUT sets up and tears down a voice call. Only applicable
3.4 3 0 Requirement: N/A
to AUTs supporting this capability.
3.4 3 1 Procedure: Initiate, maintain, and terminate a voice call from the AUT. Result: Voice call succeeds.
Repeat step 1 with the modification that the call is terminated
3.4 3 2 Procedure: Result: Voice call succeeds.
from the called party (not by the AUT).
3.4 3 3 Procedure: Exit AUT & Application Manager. Result: Return to native OEM screen.
Motivation: Ensure AUT does not interfere with ability to make
3.4 3 4 Procedure: Initiate voice call from handset using native OEM interface. outgoing voice calls from native interface. Result: Voice call
succeeds.
Motivation: Ensure AUT does not interfere with ability to
3.4 3 5 Procedure: Call handset from another phone. receive incoming calls through native interface. Result: Voice
call succeeds.
Start AUT. Initiate voice call from AUT. Terminate AUT with
3.4 3 6 Procedure: Result: Call initiate. Return to native OEM screen.
END key while initiating voice call.
Restart AUT. Initiate voice call. Terminate AUT using END key
3.4 3 7 Procedure: Result: Call established. Return to native OEM screen.
after voice call has been established.
Restart AUT. Initiate and terminate a voice call. Terminate
3.4 3 8 Procedure: Result: Call established. Return to native OEM screen.
AUT using END key while voice call is terminating.
3.4 3 9 Procedure: Restart AUT. Initiate, maintain, and terminate a voice call. Result: Call succeeds.
Exit AUT. Initiate, maintain, and terminate a voice call from
3.4 3 10 Procedure: Result: Call succeeds.
native OEM.
Repeat steps 1-10 for each AUT screen or function that
3.4 3 11 Procedure: Result: See individual steps.
initiates voice calls.
If the application did not exit, exit the AUT and then terminate
3.4 3 12 Procedure: Result: Voice call ends immediately.
the call.
Start the AUT and initiate a voice call. Abnormally exit the AUT.
3.4 3 13 Procedure: Result: Connection succeeds.
Restart the AUT and initiate a voice call.
Repeat step 3 five to ten times using different methods to
3.4 3 14 Procedure: Result: See individual steps.
abnormally exit the AUT.
3.4 4 0 Test Name: Application-Directed SMS 15 N/A
The AUT handles or ignores (as appropriate) application-
directed SMS messages, both while the AUT is running and
3.4 4 0 Requirement: N/A
when the AUT is not running. This is evaluated for all
applications.
Result: AUT receives SMS and responds as specified in the
App Spec. If AUT does not support AUT-directed SMS, AUT
With AUT running, send App Directed SMS to the AUT
3.4 4 1 Procedure: continues to operate. Note: The format of the app directed
according to formatting instructions provided in App Spec.
SMS is specified in the BREW Knowledge Base "Handling
SMS in BREW" page.
Repeat step 1 while exploring AUT on multiple screens and
3.4 4 2 Procedure: menus (e.g. 10 times). Change format of SMS message if Result: See individual steps.
possible.
3.4 4 3 Procedure: Exit and restart AUT. Result: AUT running.
3.4 4 4 Procedure: Repeat step 1. Result: See individual steps.
3.4 4 5 Procedure: Exit AUT. Exit Application Manager. Result: Return to native OEM screen.
Result: AUT receives SMS and responds as specified in the
3.4 4 6 Procedure: Send App Directed SMS to AUT. App Spec. If AUT does not support AUT-directed SMS, AUT
continues to operate.
Repeat step 6 multiple times (e.g. 5), changing format of SMS
3.4 4 7 Procedure: Result: See individual steps.
message if possible.
3.4 5 0 Test Name: Outgoing SMS (Mobile-Originated) 15 N/A
The AUT sends mobile originated SMS messages from within
3.4 5 0 Requirement: the AUT (as specified in apps spec). Only applicable to AUTs N/A
supporting this capability.

6
QUALCOMM Proprietary 80-D4187-3 Rev.A
 TRUE BREW Test Procedures
Start AUT. Send mobile originated SMS from within AUT to Result: SMS received at second handset. Content of
3.4 5 1 Procedure:
another handset. message matches that sent.
Repeat Step 1 for each AUT screen and function supporting Result: SMS received at second handset. Content of
3.4 5 2 Procedure:
mobile originated SMS. message matches that sent.
Repeat Step 2 five times with varying SMS content as Result: SMS received at second handset. Content of
3.4 5 3 Procedure:
appropriate (e.g. different messages). message matches that sent.
3.4 5 4 Procedure: Exit AUT. Exit Application Manager. Result: Return to native OEM screen.
Motivation: Ensure that AUT SMS capabilities do not interfere
3.4 5 5 Procedure: Send mobile originate SMS using native OEM interface. with native capabilities: Result: SMS received at second
handset. Content of message matches that sent.
3.4 6 0 Test Name: Timers and Alarms 8 N/A
The AUT sets and responds to timers and alarms. Only
3.4 6 0 Requirement: N/A
applicable to AUTs supporting this capability.
3.4 6 1 Procedure: Set timer and/or alarm as specified in the App Spec. Result: Timer and/or alarm setting accepted by AUT.
Wait required time. Ensure AUT behaves as specified in App Result: Upon expiration of timer and/or alarm, AUT behaves
3.4 6 2 Procedure:
Spec when timer or alarm lapses. as specified in App Spec.
Repeat for each AUT screen or function that allows setting of Result: Upon expiration of timer and/or alarm, AUT behaves
3.4 6 3 Procedure:
times or alarms. as specified in App Spec.
Result: Upon expiration of timer and/or alarm, AUT behaves
3.4 6 4 Procedure: Repeat Steps 1-3 two times using different timer values.
as specified in App Spec.
3.4 7 0 Test Name: Address Book 18 N/A
The AUT correctly handles the interface and operations on the
3.4 7 0 Requirement: OEM’s address book. Only applicable to AUTs supporting this N/A
capability.
3.4 7 1 Procedure: AUT running. Create (address) record. Result: Address record created.
Result: Address record can be viewed and is identical to
3.4 7 2 Procedure: From AUT, view address record that was created.
entered information.
3.4 7 3 Procedure: From AUT, edit address record. Result: Address record is modified to new value.
Motivation: Ensure database records persist across AUT exit
3.4 7 4 Procedure: Exit AUT. Restart AUT. View address record. and startup. Result: Address record can be viewed and has
specified values.
3.4 7 5 Procedure: Repeat Steps 1-2, adding several more records. Result: Address records created.
Motivation: Ensure interoperation with native OEM address
Exit AUT. Examine records from native OEM interface (if
3.4 7 6 Procedure: book interface. Result: Records can be viewed with specified
possible).
values.
Motivation: Ensure interoperation with native OEM address
3.4 7 7 Procedure: Modify one record from native OEM interface.
book interface. Result: Record is modified as specified.
Motivation: Ensure interoperation with native OEM address
3.4 7 8 Procedure: Delete one record from native OEM interface.
book interface. Result: Records is deleted.
3.4 7 9 Procedure: Start AUT. View records. Result: Changes on OEM side are reflected on AUT side.
If AUT provides additional phone capabilities (per App Spec),
Result: Additional features operate as specified in the App
3.4 7 10 Procedure: for example synchronization with a web-site/content-server,
Spec.
perform these additional tests.
3.4 8 0 Test Name: Data Storage 10 N/A
The AUT is able to retrieve saved data. Data may be stored
3.4 8 0 Requirement: locally on the handset or on the content server. Only N/A
applicable to AUTs supporting this capability.
Start AUT. Execute AUT screen or function (per App Spec) Motivation: Exercise data storage capabilities. Result: Data
3.4 8 1 Procedure:
that results in storage of data (to EFS or Content Server). is stored successfully.
Motivation: Ensure saved data can be retrieved. Result: Data
3.4 8 2 Procedure: View stored data. previously entered is visible, values are as specified in
previous (saving) test step.
Motivation: Ensure saved data can be retrieved through AUT
3.4 8 3 Procedure: Exit and restart AUT. View stored data. exit and startup. Result: Data previously entered is visible,
values are as specified in previous (saving) test step.
Motivation: Ensure saving of data succeeds with multiple data
3.4 8 4 Procedure: Repeat Steps 1-2 several times, creating additional records. records. Result: Data previously entered is visible, values are
as specified in previous (saving) test step.

7
QUALCOMM Proprietary 80-D4187-3 Rev.A
 TRUE BREW Test Procedures
Motivation: Ensure saved data can be retrieved through AUT
3.4 8 5 Procedure: Exit and restart AUT, View stored data. exit and startup. Result: Data previously entered is visible,
values are as specified in previous (saving) test step.
Motivation: Ensure AUT deletes data. Result: AUT deletes
3.4 8 6 Procedure: Delete several data records. View stored data.
entry. Deleted data no longer visible.
3.4 8 7 Procedure: Exit and restart AUT. View stored data. Result: Deleted data still no longer visible.
Motivation: Ensure previously created data records can be
3.4 8 8 Procedure: Modify several data records. View stored data. modified. Result: Data records are modified with values
specified by tester.
Motivation: Ensure modified data can be retrieved through
3.4 8 9 Procedure: Exit and restart AUT. View stored data. AUT exit and startup. Result: Data previously modified is
visible, values are as specified in previous (saving) test step.
Repeat Steps 1-9 for each AUT screen of function that stores,
3.4 8 10 Procedure: Result: See individual steps.
retrieves, and edits data.
3.4 9 0 Test Name: Ringers and Wallpaper 10 N/A
The AUT downloads, saves, and plays ring tones and/or
wallpaper (as specified in the App. Spec.). Downloaded tones
3.4 9 0 Requirement: N/A
or images can be accessed through the native UI. This is
applicable only to AUTs supporting this capability.
Motivation: Want to keep track of files that will be downloaded
3.4 9 1 Procedure: View shared ringer directory. Note files already within it. later. Result: List of ringer files that already exist in the ringer
directory.
3.4 9 2 Procedure: Preview ringer. Result: Previewed ring-tone plays.
3.4 9 3 Procedure: Download and save ringer. Result: Ring-tone is downloaded to handset.
Repeat Steps 2-3 for each ringer format available on content Motivation: Ensure all formats download and operate on the
3.4 9 4 Procedure: server (per App Spec) or until at least five ringers are on handset. Result: At least five ring tones have been
handset (whichever is greater). downloaded to the handset.
Exit AUT. View shared ringer directory. Note new files
3.4 9 5 Procedure: Result: Files downloaded now in directory.
created.
Using native OEM ringer interface (if available), view ringers, Motivation: Ensure interoperation between native ringer
3.4 9 6 Procedure: delete a ringer, play/preview ringers for each format, set a interface and AUT. Result: Downloaded ringers can be
ringer for incoming calls and a ringer for SMS. configured or controlled through native UI interface.
3.4 9 7 Procedure: Call handset. Send SMS. Verify select ringer is activated. Result: Selected ring-tones sound.
Start AUT. View changes to ringers (made from native OEM Motivation: Ensure interoperation betweennative ringer
3.4 9 8 Procedure: side) on AUT side. The ringer that was deleted is no longer interface and AUT. Result: Changes made on OEM side are
displayed by AUT. reflected on AUT side.
Result: Downloaded ringers can be configured or controlled
3.4 9 9 Procedure: Repeat Steps 6-7 if AUT provides similar capabilities.
through AUT interface. Selected ring-tones sound.
Result: All ringers have been deleted (as observed from AUT
3.4 9 10 Procedure: Delete all downloaded ringers from AUT.
interface).
Result: All ringers have been deleted (as observed from
3.4 9 11 Procedure: Exit AUT. View ringers from OEM ringer interface (if available).
native OEM interface).
Result: AUT supports download and configuration of
Repeat steps 1-12 for AUTs that support download of
wallpaper. Wallpaper can be accessed by native OEM (if
3.4 9 12 Procedure: wallpaper. Omit portions of procedures not applicable to
applicable). Wallpapers disappear from directory when
wallpaper (those involving SMS and incoming voice calls).
deleted through AUT.
Motivation: Ensure deletion of ringers from AUT removes files
3.4 9 12 Procedure: View shared ringer directory. from ringer directory. Result: Downloaded files removed from
ringer directory.
3.4 10 0 Test Name: Camera 19 N/A
The AUT is able to take, store, and send pictures (as specified
3.4 10 0 Requirement: in the App. Spec.). This is applicable only to AUTs supporting N/A
this capability.
Start AUT. Take photograph. Save photograph. View Result: Photographic image is created, can be stored,
3.4 10 1 Procedure:
photograph. recalled, and viewed.
3.4 10 2 Procedure: Repeat step 1, changing the brightness setting. Result: Brightness of recorded image changes.
3.4 10 3 Procedure: Repeat step 1, changing the contrast setting. Result: Contrast of recorded image changes.
3.4 10 4 Procedure: Repeat step 1, changing the display size setting. Result: Display size of recorded image changes.
3.4 10 5 Procedure: Repeat step 1, panning and zooming. Result: Recorded image pans and zooms.

8
QUALCOMM Proprietary 80-D4187-3 Rev.A
 TRUE BREW Test Procedures
Repeat steps 1 through 5, using the video (moving image) Result: Moving image is recorded and plays back. Brightness,
3.4 10 6 Procedure:
recording capability of the AUT. Playback. contrast, display size, panning, zooming function.
3.4 10 7 Procedure: Record a moving image with audio. Playback. Result: Audio is audible along with playback of moving image.
3.4 11 0 Test Name: Position Location, Non-Tracking Applications 16 N/A
The AUT supporting non-tracking position location services is
able to retrieve position fixes and use these fixes as specified
3.4 11 0 Requirement: N/A
in the App. Spec. Only applicable to AUTs supporting this
capability.
Result: AUT obtains the location fixes without error, or displays
user-friendly error if fix cannot be obtained. AUT takes the
Go to a location where there is a clear view of the sky. Force
3.4 11 1 Procedure: appropriate action upon reception of these fixes (e.g.
the application to obtain 10 consecutive position fixes.
download a map from content server and display it). Content
displayed reflects location of the tester.
Result: AUT obtains the location fixes from without error, or
Go to a location inside a building as far as possible from any displays user-friendly error if fix cannot be obtained. AUT
3.4 11 2 Procedure: windows and openings. Force the application to obtain 10 takes the appropriate action upon reception of these fixes (e.g.
consecutive position fixes. download a map from content server and display it). Content
displayed reflects location of the tester.
Force the application to obtain a position fix. While the
3.4 11 3 Procedure: Result: No adverse affect on AUT's functionality.
application is connecting to the PDE, lose wireless service.
Re-enter the wireless service area and force the application to Result: AUT obtains the location fixes without error, or displays
3.4 11 4 Procedure:
initiate a position fix. user-friendly error if fix cannot be obtained.
3.4 12 0 Test Name: Position Location, Tracking Applications 16 N/A
The AUT supporting non-tracking position location services is
able to retrieve position fixes and use these fixes as specified
3.4 12 0 Requirement: N/A
in the App. Spec. Only applicable to AUTs supporting this
capability.
Result: AUT obtains the location fixes without error, or displays
user-friendly error if fix cannot be obtained. AUT takes the
Go to a location where there is a clear view of the sky. Start
3.4 12 1 Procedure: appropriate action upon reception of these fixes (e.g.
tracking mode and move around the area for 15 minutes.
download a map from content server and display it). Content
displayed reflects location of the tester.
3.4 12 2 Procedure: Stay in a single location for 5 minutes. Result: Positions reported by the AUT do not change.
Result: AUT obtains the location fixes without error, or displays
Go to a location inside a building as far as possible from any user-friendly error if fix cannot be obtained. AUT takes the
3.4 12 3 Procedure: windows and openings. Start tracking mode and move around appropriate action upon reception of these fixes (e.g.
the area for 15 minutes. download a map from content server and display it). Content
displayed reflects location of the tester.
Start tracking mode. While the application is connecting to the
3.4 12 4 Procedure: Result: No adverse affect on AUT's functionality.
PDE, lose wireless service.
Re-enter the wireless service area and start tracking mode Result: AUT obtains the location fixes without error, or displays
3.4 12 5 Procedure:
again. user-friendly error if fix cannot be obtained.
Repeat step 1 with the modification that SMS messages are Result: Results are similar to those of step 1. AUT suspends
3.4 12 6 Procedure:
sent to the handset every 10 second. and resumes without any adverse affects.
3.4 13 0 Test Name: Screen Saver NA N/A
A screen-saver AUT can be (1) selected from the Application
Manager; (2) initiated as a screen-saver by the handset; and
3.4 13 0 Requirement: N/A
(3) terminates in response to key events. This is applicable
only to AUTs supporting this capability.
3.4 13 1 Procedure: Select AUT as screen-saver using App Manager options menu. Result: Selection succeeds.
Exit Application Manager. Let handset sit idle until screen-
3.4 13 2 Procedure: Result: Screen-saver AUT activates.
saver activates.
3.4 13 3 Procedure: Press any key. Result: Screen-saver AUT terminates.
Start a BREW app (not AUT). Let sit idle until screen-saver Result: Screen-saver AUT activates, suspending the other
3.4 13 4 Procedure:
activities. Press any key. (non-AUT) BREW app. Screen-saver terminates on key press.
3.4 14 0 Test Name: Sound Control 12 N/A

9
QUALCOMM Proprietary 80-D4187-3 Rev.A
 TRUE BREW Test Procedures
The AUT provides control over sounds as specified in the App.
Spec. Native sound settings (e.g. volume) prior to application
startup are restored on normal application termination with
3.4 14 0 Requirement: exceptions noted in the App. Spec. (e.g. application allows N/A
selection of particular ring tones that should persist after
application termination). Only applicable to AUTs supporting
this capability.
From native OEM, set volume. Initiate incoming call to handset Motivation: Take note of sound volume. Result: Ringer
3.4 14 1 Procedure:
to audit ring volume. sounds for incoming call.
3.4 14 2 Procedure: Start AUT. Turn off sound (if supported). Explore AUT. Result: No sound heard while using AUT.
Motivation: Turning off AUT sound should not interfere with
Initiate incoming call to handset. Audit ringer volume.
3.4 14 3 Procedure: native sound setting (e.g. for incoming call). Result: Incoming
Terminate incoming call and resume AUT.
call generate audible sound.
3.4 14 4 Procedure: Adjust sound volume. Explore AUT. Audit sounds. Result: Modifications to sound volume are audible.
3.4 14 5 Procedure: Repeat Step 4 for several adjustments (e.g. four). Result: Modifications to sound volume are audible.
3.4 14 6 Procedure: Adjust volume up to maximum level. Result: Modifications to sound volume are audible.
Motivation: Ensure that sounds from AUT are muted
Initiate incoming call to handset. Audit ringer volume. Ensure
(suspended) on incoming call or other suspension event.
3.4 14 8 Procedure: AUT sounds are muted so ringer is only heard. Answer call.
Then AUT sound continues on resume. Result: AUT sound
End call. Resume AUT.
mutes and unmutes in conjunction with suspend and resume.

Exit AUT. Exit Application Manager. Through native interface,

mute ringer volume. Call handset. Start AUT. Turn AUT Motivation: Ensure that muted ringer volume is not affected by
volume up to maximum value. Initiate incoming call to AUT volume set to audible (maximum) levels. Result: Ringer
3.4 14 9 Procedure:
handset. Audit ringer volume. Terminate call. Resume AUT. does not sound when AUT is suspended or from native
Exit. Initiate incoming call to handset. Audit ringer volume. interface after AUT exits.
Terminate call.

3.5 0 BREW User Interface

3.5 1 0 Test Name: Clear Key NA N/A
The Clear key moves the user up (back) one level in the AUT
3.5 1 0 Requirement: menu hierarchy. Use of the Clear key at the AUT’s root menu N/A
terminates the application.
Starting from main AUT menu, explore a particular menu path
3.5 1 1 Procedure: Result: AUT returns to previous screen.
on the AUT to its end points. Press the CLR key.
3.5 1 2 Procedure: Repeat Step 1 until arrival at main menu. Result: AUT returns to previous screen.
3.5 1 3 Procedure: Repeat steps 1-2 for all menu branches of the AUT. Result: AUT returns to previous screen.
Starting from main AUT menu, explore a particular menu path
3.5 1 4 Procedure: Result: Text box available for entry and editing.
until arrival at a editable text box.
Result: Pressing clear key deletes character to left of current
3.5 1 5 Procedure: Enter text characters. Press CLR key. cursor position. AUT allows a return to previous screen
(through use of Clear Key or other soft key).
Result: Pressing clear key deletes character to left of current
3.5 1 6 Procedure: Repeat Steps 4-5 until all editable text boxes evaluated. cursor position. AUT allows a return to previous screen
(through use of Clear Key or other soft key).
3.5 1 7 Procedure: Start AUT. Press CLR key. Result: AUT exits to Application Manager.
Motivation: Ensure setup of data call can be cancelled (before
Start AUT. Initiate data call (network AUT only). Immediately it is established) with Clr key. Result: AUT terminates
3.5 1 8 Procedure:
press CLR key. establishment of connection, returns to state prior to
connection setup.
Motivation: Ensure data transfer can be cancelled with Clr
Stat AUT. Initiate and establish data call (network AUT only).
3.5 1 9 Procedure: key. Result: AUT terminates transfer returns state prior to
Press CLR key during data transfer.
establishment of connection.
3.5 2 0 Test Name: Send Key 13 N/A
The AUT correctly handles the use of the Send key. This key is
not used except for predefined operations associated with
3.5 2 0 Requirement: N/A
external over-the-air communications (voice calls, data calls, or
mobile originated SMS).

10
QUALCOMM Proprietary 80-D4187-3 Rev.A
 TRUE BREW Test Procedures
Result: Send key performs functions identified in application
Operate AUT. Navigate to screens or functions that use the specification.; All screens that use send key are identified.;
3.5 2 1 Procedure:
send key. Press the send key. Send key is only used to perform one of the following
functions: ; Voice call.; Data call.; Mobile originated SMS.
Repeat Step 1 for all AUT screens and functions that use the
3.5 2 2 Procedure:
Send key.
3.5 3 0 Test Name: Response Time NA N/A
The AUT informs the user with visual feedback when there are
3.5 3 0 Requirement: N/A
delays greater than 3 seconds in duration.
Motivation: Users can become frustrated or confused if AUT
Start AUT. Explore AUT. Identify operations that take longer does not provide indication that it is functioning (and not hung
3.5 3 1 Procedure: than 3 seconds without providing any indication to the user up of frozen). Result: User is notified with visual feedback if
(such as an rotating symbol or completion bar). there is a processing delay greater than approximately 2
seconds.

3.6 0 Adversarial
3.6 1 0 Test Name: Loss of Service NA N/A
The AUT gracefully handles no-service and loss-of-service
conditions. A no-service condition will result in connection
failure when the AUT attempts to establish a connection. A
3.6 1 0 Requirement: N/A
loss-of-service condition will affect the AUT after a connection
has been established. The requirement applies to applications
using data services or voice services.
Prepare AUT to initiate data call (do not start data call). Place
handset in Hoffman Box for 30 seconds. Remove handset Motivation: Ensure AUT handles loss-of-service during call
3.6 1 1 Procedure: from Hoffman Box briefly, ensure no service (via annunciators), setup. Result: AUT detects and responds to loss-of-service
initiate data call, place handset back into Hoffman box for 1 (e.g. reports error to user).
minute. Remove handset and view AUT.
Motivation: Ensure AUT error handling for loss-of-service
does not affect ability to successfully make data call once
3.6 1 2 Procedure: Initiate data call after handset has re-acquired service. service restored. Result: AUT succeeds in making data call
and transferring data, functioning as it did during exploratory
testing.
Initiate and establish data call. As AUT is transferring data Motivation: Ensure AUT handles loss-of-service during data
3.6 1 3 Procedure: across data connection, place handset in Hoffman Box for transfer. Result: AUT detects and responds to loss-of-service
approximately 1 minute. Remove handset from Hoffman box. (e.g. reports error to user).
Motivation: Ensure AUT error handling for loss-of-service
does not affect ability to successfully make data call once
3.6 1 4 Procedure: Initiate data call after handset has re-acquired service.
service restored. Result: AUT succeeds in making data call,
functioning as it did during exploratory testing.
Motivation: The intent is to determine how an application
handles loss of a connection that is idle or dormant after
Let handset sit idle after transfer is step 4 for linger timer plus
3.6 1 5 Procedure: already successfully transferring data across it. Result: AUT
20 seconds. Repeat step 1.
detects and respond to loss-of-service (e.g. reports error to
user).
Note: The purpose is to evaluate different screens or
Repeat Steps 1-5 for each AUT screen or function that functions provide by the AUT, not to evaluate different content
3.6 1 6 Procedure:
transfers data across a data connection. types on a server that are available through the same AUT
screen. Result: See individual steps.
Motivation: AUTs supporting voice calls will have similar
problems with call setup and maintenance. Repeat above
Repeat steps 1-6 (as applicable) for an AUT that supports
3.6 1 7 Procedure: steps for voice calls instead of data calls. Result: AUT
making voice calls.
supporting voice calls detects and responds to loss-of-service
(e.g. reports error to user).
Motivation: Ensure that AUT handles inability to send an SMS
Repeat step 1 for AUT that supports sending of SMS
message. Result: AUT supporting sending of SMS messages
3.6 1 8 Procedure: messages. Instead of making data call, initiate SMS. Other
detects and respond to loss-of-service (e.g. reports error to
steps the same as step 1.
user).

11
QUALCOMM Proprietary 80-D4187-3 Rev.A
 TRUE BREW Test Procedures
Motivation: Differences in underlying networks may affect
Repeat steps 1-8 for each network protocol supported by the
AUT error handling. Result: AUT detects and responds to
3.6 1 9 Procedure: handset (e.g. CDMA 2000 1X, IS-95B, EVDO, GPRS, W-
loss-of-server for data and voice calls on each underlying
CDMA).
network.
3.6 2 0 Test Name: Dynamic Displays NA N/A
Dynamic AUT displays (e.g. displays that change continuously
3.6 2 0 Requirement: without user input) are stable for long periods of time (e.g. 5 N/A
minutes).
Motivation: Ensure that AUT is stable when autonomously
Start the AUT. Explore application, identifying a screen that
3.6 2 1 Procedure: performing repeated operations as occurs on a dynamic
remains active (e.g. moving graphics or text) without user input.
display. Result: Identified screen is active without user input.
Allow AUT with dynamic display to continue activity for 30
3.6 2 2 Procedure: Result: No adverse affects. AUT continues to function.
seconds.
Repeat Steps 1-2 for all screens with activity that remains
3.6 2 3 Procedure: Result: No adverse affects. AUT continues to function.
dynamic without user input.
3.6 3 0 Test Name: Continual Keypad Entry NA N/A
The AUT is robust in the face of a rapid succession of random
3.6 3 0 Requirement: N/A
keypad inputs.
Motivation: Ensure AUT handles large buffer of random key-
Start AUT. Once started, rapidly press keys for 10 seconds. presses. Result: AUT handles all keypad input by either
3.6 3 1 Procedure:
Omit End key and Clear key. correctly processing it or ignoring it. No adverse affect on AUT
or handset.
Note: If adverse affects observed, tester should try to
determine whether a particular key is causing problems (or if
Repeat step 1 for each AUT screen and function, including
3.6 3 2 Procedure: problem is result of rapidly pressing any key). Result: AUT
point in AUT for which data calls have been established.
handles all keypad input by either correctly processing it or
ignoring it. No adverse affect on AUT or handset.
Motivation: Ensure AUT handles or limits large strings.
Navigate to a data entry (editable text field). Rapidly press
3.6 3 3 Procedure: Result: AUT either accepts large strings or limits size. No
random keys for 10 second to create a large string.
adverse affect on AUT or handset.
Motivation: Ensure AUT handles or limits large strings.
3.6 3 4 Procedure: Repeat Step 3 for each editable text box presented by AUT. Result: AUT either accepts large strings or limits size. No
adverse affect on AUT or handset.
3.6 4 0 Test Name: AUT Stability NA N/A

3.6 4 0 Requirement: The AUT is stable when running over a long period of time. N/A

Motivation: Setting time forward will evaluate for time-based

behaviors. And emulator will detect memory leaks when
Set date on test PC forward five years. Run AUT on Emulator.
application terminates. Intent is to exercise sections of code
3.6 4 1 Procedure: Perform exploratory testing, traversing the AUT screens and
that may allocate memory and/or have time-base behaviors.
functionality. Exit AUT.
Result: (1) Emulator does not report a memory leak. (2)
Application has no undocumented time-based behaviors.
Run the AUT using the Grinder on handset with the following Result: AUT operates in response to grinder key-events with
3.6 4 2 Procedure: settings: 10 Grinds with 1000 Events per Grind with 250 ms no adverse affects (AUT crash or hang, handset crash or
between each Grind. hang, etc).
Run the AUT using the Grinder on the BREW Emulator with
Result: AUT operates in response to grinder key-events with
the following settings: three years using the day based option
no adverse affects (AUT crash or hang, handset crash or
3.6 4 3 Procedure: under the Hidden Grinder settings (TBT tester only); 5 Grinds
hang, etc). Emulator does not report memory leak on AUT
with 10 Events per Grind with 250 ms between each Grind. On
exit.
completion, exit AUT.
3.6 5 0 Test Name: Low Flash Memory NA N/A
The AUT must be stable (e.g. does not crash handset and
gracefully terminates execution) when faced with low
3.6 5 0 Requirement: Embedded File System (EFS) conditions (e.g. in the face of file N/A
create and write failures when attempting to write to flash
memory).
Motivation: Creating the maximum number of files fills the
Run the MaxFileCount utility on the handset until the maximum BREW directory space of the handset, creating condition in
3.6 5 1 Procedure:
number of files has been created. which file creates by AUT will fail. Result: Maximum number
of files created.

12
QUALCOMM Proprietary 80-D4187-3 Rev.A
 TRUE BREW Test Procedures
Motivation: Ensure that AUT does not crash nor unstable
Start AUT. Navigate through AUT, focusing on screens and
when file creations fail. Result: AUT detects and responds to
3.6 5 2 Procedure: functions that are known or expected to result in the creation of
file creation failure (e.g. notifies the user with an error
files.
message).
Motivation: AUT may create multiple files. Removing one file
allows AUT to create one file, then fail. This may test
3.6 5 3 Procedure: Run MaxFileCount application, removing one file.
additional file creation code segments of the AUT. Result:
One less file on handset.
Motivation: Ensure AUT handles file creation failure. Result:
Start AUT. Navigate through AUT, focusing on screens and
3.6 5 4 Procedure: AUT detects and responds to file creation failure (e.g. notifies
functions that are known to result in the creation of files.
the user with an error message).
Repeat Steps 3-4 until AUT operates normally (can create all Result: AUT detects and responds to file creation failures until
3.6 5 5 Procedure:
files it needs). it can create all the files it requires.
This procedure currently not performed. Creating the
Motivation: Free up directory space on handset. Result:
appropriate test condition not possible on many
3.6 5 6 Procedure: Remove files created by MaxFileCount application. MaxFileCount files removed. Can be verified by viewing
handsets. This procedure will be re-instituted in the
directory through App Loader.
future.
Run Shaker, creating a large file that consumes all free Flash Motivation: Starve application of file space so file writes fail.
3.6 5 7 Procedure: See above note.
memory. Result: Large file created.
Motivation: Observe response (error handling) of application
Start AUT. Navigate through AUT, focusing on screens and
3.6 5 8 Procedure: in face of file write failures. Result: Application detects and See above note.
functions that are known to write data to Flash memory.
respond to file write failures.
3.6 5 9 Procedure: Remove file created by Shaker application. Motivation: Cleanup handset. Result: File removed. See above note.
3.6 6 0 Test Name: Low RAM Memory NA N/A
This test currently not performed. Creating
The AUT must be stable (e.g. does not crash handset and
appropriate test condition is difficult or impossible
gracefully terminates execution) when faced with low RAM
3.6 6 0 Requirement: N/A using current set of test tools (e.g. Shaker). This
memory conditions (e.g. in the face of memory allocation
test will be re-instituted in the future with the release
failures).
of new test tools.
Motivation: The goal is to starve the AUT of additional
Start AUT. Determine largest block of free RAM using "###3" memory after startup. Therefore first look at free memory with
3.6 6 1 Procedure: See above note.
debug display. AUT started up and sitting on first screen (e.g. main menu).
Result: Free memory determined.
3.6 6 2 Procedure: Exit AUT. Result: Return to Application Manager screen. See above note.
Result: Shaker allocates requested memory and then
3.6 6 3 Procedure: Start Shaker. Configure to consume free memory minus 1K. See above note.
suspends in the background, holding onto this memory.
Start AUT. Perform exploratory. Focus on AUT operations and Result: AUT operates as during exploratory testing or AUT
3.6 6 4 Procedure: features that may involve memory allocation (e.g. download of detects and responds to memory allocation failure (e.g. reports See above note.
content from server or higher levels of a game). error to the user).
3.6 7 0 Test Name: Exit AUT 4 N/A
The AUT terminates execution in response to a Clear Key
(when invoked from the root application menu), any means
3.6 7 0 Requirement: described in the App. Spec. (e.g. menu selection), the End N/A
Key, and other OEM specific means (e.g. closing the clam-
shell). The AUT can be started and operated after termination.
Start AUT. Operate AUT. Exit AUT using means of exit Result: AUT starts up, operates, and exits to the Application
3.6 7 1 Procedure:
specified in App Spec (e.g. "Exit" menu options). Manager.
Repeat Step 1 for all ways to exit AUT as specified in the App Result: AUT starts up, operates, and exits to the Application
3.6 7 2 Procedure:
Spec. Manager.
Motivation: Ensure AUT handles other means of AUT
Start AUT. Operate AUT. Exit using one of following means:
3.6 7 3 Procedure: termination (such as End key). Result: AUT starts up,
End Key, closing clam shell, other handset specific means.
operates, and exits to the Application Manager.
Motivation: Test AUT exit on a random sampling of screens to
Repeat Step 3 on additional screens using different means of
3.6 7 4 Procedure: determine whether any termination problems. Result: AUT
exit.
starts up, operates, and exits to the Application Manager.

3.7 0 Application Download

3.7 1 0 Test Name: Disable and Restore NA N/A

13
QUALCOMM Proprietary 80-D4187-3 Rev.A
 TRUE BREW Test Procedures
The AUT can be disabled and restored once loaded on a
3.7 1 0 Requirement: mobile handset. Persistent state (stored data) results are not N/A
lost.
Motivation: Some applications lose important user state after
Start AUT. Operate AUT screens and features that save data.
disable/restore operation. Therefore, operate AUT to store
3.7 1 1 Procedure: This state can be achieved by performing this test after
data on handset and/or content server. Result: Data stored
completing exploratory testing.
on handset and/or content server.
Disable the AUT. BREW 1.0, 1.1, 1.2: Disable from Mobile
Shop Options menu. BREW 2.0 and up: Disable by Result: AUT disabled (MOD, BAR, and SIG files no longer
3.7 1 2 Procedure: downloading Apps until handset is full, then select to remove present on handset). Note that files will appear in multiple
AUT when prompted by Mobile Shop. View AUT directory to directories if the app is multi-module.
ensure MOD and BAR removed.
Enable AUT. For BREW 2.0 and up, this requires first
removing the additional App that was downloaded. For
Result: AUT BAR, MOD, and SIG files downloaded to AUT
developer, copy without replace all files back onto the handset.
3.7 1 3 Procedure: directory. Both files appear in directory. Note files may
This will move back onto the handset BAR and MOD files, as
appear in multiple directories if the app is multi-module.
well as files that were renamed or deleted by the AUT during
exploratory testing.
Start AUT. Ensure data saved prior to Disable is not lost. Result: AUT can be started and operated. Data stored on
3.7 1 4 Procedure:
Perform limited exploratory to verify AUT still functions. handset and/or content server is available.
3.7 2 0 Test Name: Application Recall NA N/A
3.7 2 0 Requirement: The AUT can be recalled by an ADS. N/A
Result: AUT completely removed from mobile handset.; AUT
Configure test server to recall AUT. Start Mobile Shop on
3.7 2 1 Procedure: no longer displays in application's menu.; User notified that
handset. Connect to application server (test server).
AUT removed (if the handset is capable of this).
Result: AUT no longer appears in Application Manager. AUT
Exit Mobile Shop. Verify absence of AUT through Application
3.7 2 3 Procedure: directory (directories for multi-mode AUT) no longer present on
Manager and by inspecting BREW directory using App Loader.
handset.

14
QUALCOMM Proprietary 80-D4187-3 Rev.A