J2ME Test Suite Homepage

What Is The J2ME Test Suite?

The J2ME Test Suite is a collection of testing tools for testing mobile devices. These tools are writing in Java using the Mobile Information Device Profile. The test suite consists of several components, including:

RMStress Test Suite

J2ME Test Suite Welcome to the J2ME Test Suite website! Here you can find information, links and development information for the J2ME Test Suite. What is the J2ME Test Suite? Download the files here What is the RMStress test suite? Where can I get the source code? Who are the developers?

What Is The RMStress Test Suite? The RMStress Test Suite has as its purpose to provide information on how efficient the `javax.microedition.rms` implements is on a given device. It goes through steps to create, open, close, delete, write to and read from multiple record stores. For this particular test suite, lower numbers indicate better performance on the device. The figures returned indicate the total time required to perform each operation, and also returns an average time per individual step in each test. So, if 100 stores are created and the total time required was 12500ms, then an average of 125ms per record store is returned.
How To Use The RMStress Test Suite
From the main screen, first select the number of records for the test run. Some devices will have a limited amount of memory dedicated to the record store layer (the specification only requires a minimum of 8k of memory for RMS) so be aware of the limitations of your device.
The actual tests that are executed are store creation, opening and closing, writing to a single store multiple records, reading records from the store, and record store deletion. First, the suite deletes any existing record stores within the MIDlet suite's sandbox (don't be alarmed, it can only delete record stores that were created by RMStress; see the MIDP specification for information on record stores and the security sandbox). This step is not included in the overall performance evaluation. It then creates the number of record stores selected on the main screen. It then iterates over the created stores and opens and then closes each of them. It then selects a single record store and writes 500 records that are 512 bytes each to the store. Each record consists of random bytes, and each record will contain the same array of bytes. It then iterates over the store, rereading the records written. Finally, the store deletes all record stores in the MIDlet suite's sandbox.
For each step listed above, the test determines how long the overall operation had taken to complete. It then determines the average time for each individual operation and displays this on the results screen, shown to the right.
Who Is On The Development Team?
Darryl L. Pierce, Project Lead Darryl has been working with Java technologies since 1995 when it was first made available. He has also been working with J2ME and the MIDP since 1999. Additionally, he has written multiple products using Java servlets, Enterprise Java Beans and Java Server Pages. He's the maintainer of the J2ME FAQ and can be found participating in both the KVM-INTEREST mailing list and also Motorola's SDKList for developers.
[$Id: index.html,v 1.1.2.2 2005/05/28 12:24:07 mcpierce Exp $]