Please note that as of October 24, 2014, the Nokia Developer Wiki will no longer be accepting user contributions, including new entries, edits and comments, as we begin transitioning to our new home, in the Windows Phone Development Wiki. We plan to move over the majority of the existing entries. Thanks for all your past and future contributions.

Revision as of 00:46, 27 July 2013 by hamishwillee (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Java Verified

From Wiki
Jump to: navigation, search
Article Metadata
Created: User:Nobody (27 Feb 2007)
Last edited: hamishwillee (27 Jul 2013)



Java Verified ([1]) is an industry wide and commonly used testing and certification program for Java ME applications. Nokia supports the program and acts as an active member in developing the program further.

Getting started

First off, the developer should read the [3 0 FINAL.pdf Unified Test Critera] and perform some internal testing him/herself to make sure the application matches the criteria used in the testing, increasing its chances of getting approved.

Following it, developer should create an account at You can submit your application (JAD and JAR) to the web portal, then select a test house. The test house will make contact and give more instructions. Once the application is tested and approved, the test house will sign your application with Java Verified Program Certificate. The signed application will be available for download from the web portal.

Warning.pngWarning: MIDlet attributes must be the same in both JAR manifest and the JAD! Otherwise the application will not work after being signed.
For more information on signing and Java verfied see this FAQ. In particular topics "Signing Java ME applications" and "Why doesn't my signed midlet work?"

Test houses

There are four test houses in the program:

  • Babel Media - UK
  • NSTL - Blue Bell, USA
  • RelQ - Bangalore, India
  • Sogeti (part of Capgemini) - Grenoble, France

Testing process

The testing program consists of three parts:

  • Free, automated pre-testing
  • UTC Test (Unified Testing Criteria)
  • Digital signing of the MIDlet

Although the tests don't cover all aspects of a well-working MIDlet, the testing is quite extensive and is divided into 10 areas:

  • General MIDP Application Launch
  • General MIDP User Interface
  • General MIDP Functionality
  • General MIDP Security
  • General MIDP Network
  • General MIDP Localization
  • JTWI MIDP 2.0 User Interface
  • JTWI MIDP 2.0 Operation
  • JTWI WMA 1.1 (Wireless Messaging API)
  • JTWI Bluetooth

A good knowledge of the testing criteria, and keeping these in mind during the design phase of the project, will almost certainly help in passing the tests.

For their contact information and prices, see [2] -> Select test provider.

This diagram shows the signing process:

This page was last modified on 27 July 2013, at 00:46.
131 page views in the last 30 days.