TestSuite 1.1.0

1. The Phone specs section can be used to quickly check the "vital statistics" of a new device. It shows the screen dimensions and color depth, the standard system properties (platform etc.), the Canvas properties, an estimate of the smallest timer resolution (e.g. the shortest time you can practically set a timer for), and reports on which JSRs have been implemented. If you've never seen a device before, and have the chance to run only one app on it, then this would be it.
2. The Class browser section provides much more detail than Specs. It utilises a database of many known Midlet classes to probe the device for which classes are present. You can browse through the hierarchy of classes found to find out the extent of support for different features, which proprietary libraries exist, and potentially discover undocumented features. Some features of a device are not exposed in classes, but many are, so this is a good way to find most of them.
3. The Keys section is an interactive tool for finding out how the phone keypad behaves. As user-input is vital for most applications that implement the Canvas object (including almost every game!), this is extremely useful information to get. With this Midlet, you can test which keys can generate concurrent events (e.g. can a user move and shoot at the same time?), find out if every key generates every necessary event (not all devices implement the Repeated event), establish which keys correspond to what game keys, and get the key codes for the non-standard keys on the device.

Enhancements:

• Test result renamed
• Result mapping updated
• More tests (Motorola, Samsung, Nokia, SonyEricsson)
• Command handling optimizations
• Send data in multiple posts
• TestSuite post data
• Optional tests
• Benchmark refactory
• Refactory. Inspector introduced.

Requirements:

• MIDP 2.0
• CLDC 1.0