Testing and signing

Testing is one of the most important phases of the application development process. Application testing is typically based on the V-Model, which defines the design and testing levels. You can find more information about the V-Model at en.wikipedia.org/wiki/V_model. Application testing and signing programmes perform testing at the application-acceptance-testing level to ensure that your application meets the model’s requirements. This means that Symbian Signed and Java™ Verified Program criteria documents must be used when considering application requirements.

Documentation
Download Nokia test criteria and other important documents.

Discussions
Discuss testing, signing, and certification issues and share ideas with other developers in our Discussion Boards.

Webinars
Check webinars about signing and certification.

eLearning
Learn more about Symbian Signed.

FAQ
Check the most common questions about testing.

Wiki
Check out the testing pages in the Forum Nokia Developer Wiki.

User Experience
See other aspects of user experience.

Why should I care?

All mobile applications offered through the Nokia sales channels must be tested and signed through either Java Verified or Symbian Signed. Forum Nokia supports these programmes and participates in developing and improving them to serve you better.

S60 3rd Edition requires that all SIS files, which are used to provide content to S60 devices, be signed. The capabilities required by the application determine the form of signature which can be used.

The following image displays the capabilities available and the form of service to be used to sign the SIS file when the application is being tested.

To access the user-grantable capabilities, the SIS file must be signed. Carbide.c++ automatically signs the SIS file when it is being created; for a manual process, the SDK includes makekeys.exe, which can be used to create keys to sign the SIS package with signsis.exe. Both tools are command-line tools.

The Open Signed services are available through Symbian Signed. You can find more information about the services at www.symbiansigned.com.

When you're ready to take your application to market, you can choose the channel best suited for your offering. The channel options are displayed in the following image. Please bear in mind that if the sales channel doesn't require Symbian Signed and the application capabilities don't require it, the SIS file can be signed using the self-signing methods discussed earlier. Nokia’s channels require your application to be Symbian Signed.

To learn more about Symbian Signed, please read the Complete Guide to Symbian Signed, which is available, like the services, from the Symbian Signed website at www.symbiansigned.com.

More information about Symbian Signed for Nokia and accessing AllFiles, DRM, and TCB is available in the document Symbian Signed: Accessing Manufacturer Capabilities.

What resources can I use?

• Nokia Energy Profiler
• Additional Nokia criteria for native Symbian C++ or Java ME Applications

How do I test?

The test houses within the Symbian Signed and the Java Verified programmes use lead devices when testing applications. Nokia has defined device platforms based on the screen size, feature set, and platform version of different devices, and each platform has one lead device. Test houses conduct application testing on a lead device once, and then assume that the application will run on the other devices in the platform.

Although there are no prototypes for Symbian Signed and Java Verified, Nokia provides lead devices to the test houses as soon as they are available. The device lists can be found on the Java Verified and the Symbian Developer Network websites.

How do I distribute it?

Nokia offers you consumer and enterprise sales channels. Each channel offers unique features and benefits for you and your customers. The consumer market channels are Nokia Software Market, Download!, and MOSH. The enterprise channel is the Nokia for Business channel programme.