Application Testing

Testing Process
Submission Process
Testing Support
Handling of BREW® Extensions

Testing Process

An application must pass TRUE BREW® compatibility testing before a developer can create a price plan for an Operator that participates in the Standard BREW program. The creation of the price plan allows the Operator to evaluate the application for inclusion on a commercial application catalog. If the Operator chooses to accept the price and include the application on a commercial catalog, the application will be available for download and use on the specified BREW handset.

The developer can make an application available to an Operator, as described above, by following these steps:

• Developer creates an application
• Developer creates an Application Specification using the template provided by Qualcomm.
• Developer tests the application
  • against all application functional requirements
  • against TRUE BREW requirements (documented in the
  • TRUE BREW Test Guide).
  • against specific Operator requirements (see Operator Guidelines)
• Developer prepares submission for TRUE BREW Testing (see Submission Process)
• Developer submits application to an authorized TRUE BREW Test Center (see Submission Process), including with the submission the test results that are documented in the TBT Test Procedures (this will be required on 5 January 2004).

TRUE BREW Testing then evaluates whether the BREW application meets the requirements specified in the TRUE BREW Test Guide. This includes evaluating the stability, quality, and compliance of the application with handset requirements. The handset requirements are specified in the appropriate Device Data Sheet (see BREW Devices).

TRUE BREW Testing evaluates the application in the following areas:

• Entrance Criteria
• Exploratory Testing
• andset/AUT Interaction
• BREW Features
• BREW User Interface
• Adversarial
• Application Download Server

If an application fails the Entrance Criteria, it is cancelled. Otherwise all of the above remaining test areas are executed. The developer will then receive a test report containing the testing status (e.g. pass/fail) and the specific test results (errors and issues).

An application that passes TRUE BREW testing will receive either the TRUE BREW status or the TRUE BREW Passed-with-Notes status. The TRUE BREW status is assigned to an application that passes all test requirements. The TRUE BREW Passed-with-Notes status is assigned to an application having minor errors that do not impact the end-user experience.

back to top

Submission Process

The process for submitting an application or extension for TRUE BREW Testing includes:

1. Prepare application for submission.
   • For BREW 3.1 applications click here.
   • For BREW 2.x and Earlier applications click here.
2. Login to NSTL's BREW Developer Registration page at https://www.nstl.com/nstl/index.htm.
3. Follow the instructions to "Submit New Application"
4. Testing times will vary based on application complexity and the number of applications in the test queue. Check under "Status of Existing Application" to monitor the application through the test process.

back to top

Testing Support

Documents related to testing are available under Testing Documentation.
For additional tips on testing, see the BREW Technical FAQs.

back to top

Handling of BREW Extensions

For background on the BREW Extension program, please refer to the Extension Program web page.

BREW public extensions are tested through a sample-application provided with the extension.

Once the TRUE BREW test lab receives the public extension and sample-application, the testing process will begin. The sample-application and public extension are considered as a bundle. This combination is tested as a single unit (black box). If the bundle fails TRUE BREW testing, the test lab does not diagnose the problem (i.e. whether the failure is located in the sample-application or extension). The extension and sample-application collectively are failed and will have to be re-submitted to TRUE BREW testing after the developer diagnose the source of the problem.

If the sample-application passes TRUE BREW testing, the public extension will be made available to other BREW Developers on the Developer Extranet and listed on the BREW Extensions List.

back to top