MobileSuite - Test Suite

Anonymous (anonymous@undisclosed.example.com) — 2019-01-19T16:07:07+0000

MobileSuite - Test Suite

The TestSuite is a suite of Java utilities that can be used by developers in the creation of new J2ME software for mobile devices. They give a developer a good way to explore the capabilities and limitations of phones and other devices, and come up to speed quickly with new devices.

Description

The Phone specs section can be used to quickly check the “vital statistics” of a new device. It shows the screen dimensions and colour 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.

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 tool, 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.

The Class browser section provides much more detail than Specs. It uses 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.

Screenshots

Test Suite Report

See handset reports.

Requirements

The game needs a MIDP2.0 compatible handset. See compatibility with real devices.

Supported languages:

Download

Test Suite can be downloaded in the “Applications” section of the Mobile portal.

The full distribution, including source code, can be downloaded here.

Additional project resources are hosted in a Source Forge Repository.

Development

To Do

Better UI
More tests

Changes log

Version 1.1.0

Aligned with MobileSuite - libJ2ME 1.1.0
Test result renamed
Result mapping updated
More specific tests (Motorola, Samsung, Nokia, SonyEricsson)
Command handling optimizations
Send data in multiple posts
TestSuite post data
Optional tests
Benchmark refactory
Refactory. Inspector intruduced

Version 1.0.0

First public release

Project status

Status: Release

Language: Java

Software metrics.

Licenza & Copyright

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program; if not, write to the:

Free Software Foundation, Inc. 59 Temple Place, Suite 330 Boston, MA 02111-1307 USA

Test Suite is based upon Mobile Device Tools application written by Andrew Scott.

Test Suite, MobileSuite, Software, Java

Technology cross

Anonymous (anonymous@undisclosed.example.com) — 2019-01-19T16:07:07+0000

Technology cross

Definition

Technology cross is a visual way to show how a product/technology is compared to other products and other alternatives.

Given a comparison scenario the cross is filled is placing in the center the evaluated product. On the vertical are placed the other products, putting on top the similar or better ones and on bottom the worst.

On the wide there are alternatives, that means different technologies that can do the same or a similar task (e.g. an online disk could be an alternative to an online backup) on the left the better alternatives, on the right worse ones.

The graph will be sometime like:

	A - similar or better products
B - better alternatives	Reference product	C - worst alternatives
	D - worst products

Formally if a comparison is done on a set of requisites (criteria), the A sector is filled with all the products that have a not worse evaluation on that criteria (compared to the reference product), the D sector with the products with a worse evaluation.

The B sector will be fill with the technologies alternative for which the will be possible to have a super set of requisites, the super set will include all the vetoable criteria and a set of other criteria that could be considered not worse that the reference set.

Last C sector will be filled with the alternatives for which will be possible to define a set of similar criteria, but that will not include all the vetoable ones.

Examples

A innovative winning product


	Best new product	Alternative 1
	Product 1 Product 2 Product 3 Product 4 Product 5 Product 6 Product 7

A winning product

	Product a
Alternative a	Winning product	Alternative 1
	Product 1 Product 2 Product 3 Product 4 Product 5 Product 6

A looser product

	Product a Product b Product c Product d Product e Product f
Alternative a	Looser product	Alternative 1
	Product 1

An old technology product

	Product a
Alternative a Alternative b Alternative c Alternative d Alternative e Alternative f		Alternative 1
	Product 1

Technology cross

eIrOcA

MobileSuite - Test Suite

MobileSuite - Test Suite

Description

Screenshots

Test Suite Report

Requirements

Download

Development

To Do

Changes log

Project status

Licenza & Copyright

Technology cross

Technology cross

Definition

Examples

A innovative winning product

A winning product

A looser product

An old technology product