Symbian Application Testing

Symbian Application Testing
In 2004 Symbian announced a common Symbian application testing and signing program called Symbian Signed ( That has gained vast industry support and is required by several sales channels and operators globally.
Symbian Signed is an industry-backed scheme allowing Symbian OS software developers to obtain a digital signature for their applications. In order to obtain such a signature, the company or individual responsible for the development of the application must be clearly identified and the application must pass certain tests. This allows the originator of the application to be traced should any problems occur in the future and ensures that the signed applications meet certain minimum standards.

Process that needs to be followed to get an application signed.

  • Register for an ACS (Authenticated content signing) Publisher ID from VeriSign (which costs $350).Your own ACS Publisher ID can be used to sign an unlimited number of applications, though you will need to renew it on annual basis.
  • Sign your .SIS file with your ACS Publisher ID.
  • Submit your application for testing using
  • Your application is tested by the TEST HOUSE against set test criteria. You will then need to pay the Test House to test your application against the Symbian Signed criteria.The cost of this varies between applications.
  • If the application passes the tests your application will be able to download your Symbian Signed application.


Requirements for Testing

Basic Hardware and Software Requirements for the Developer

The minimum requirements for all developers are:

  • Two subscriber connections (including Subscriber Identity Module [SIM] cards)
  • Two devices
  • PC Suite/Symbian OS software and infrared and/or Bluetooth connection
  • Optionally, a printer with infrared and/or Bluetooth capacity

Fundamental requirement

There are few fundamental requirements that developer should be taking care of when developing any symbian application they are:

* Non technical issues

Developers should check that:

  • The content of the application is acceptable.
  • The developer has rights to use all the brands visible in the application.
  • Application Performance and Reliability

Developers should check that:

· The application speed does not compromise the use and purpose of the application

· The application does not consume the device’s running power and memory excessively.

· The application does not affect the use of the system features or other applications.

· The application does not cause any harm to the user, other applications, or data.

· There are no bottlenecks in the code.

· Communication to and from the device/application is kept within reasonable limits.
o Application Security

A mobile device is carried everywhere by its owners. Because of this fact, there is always a risk that the device will be lost. Therefore, no sensitive data should be stored in a mobile device without encryption.

o Packaging and Installation

Developers should check that:

· If registration code is needed when installing, instructions are displayed for obtaining the code.

· The application creates and installs to the defined destination.

· The application starts up in a reasonable time period (five seconds) or provides appropriate progress indication. The application can be started from the C: or D:/E: drive.

· No absolute file paths are defined in the *.pkg file.

o Removal and Reinstallation

Removing (uninstalling) the application must be easy and straightforward. Uninstall must provide complete removal of all files and the installed data, including any icon files.

We can perform functional, usability, memory and localization testing.

Testing tools can be used for Lists files and disk space usage, Memory Load, File Storage Load and OS Profiler/task list etc.
image credit:

Get A Free Quote