Java Device Test Suite Administration Guide

The Java Device Test Suite can work with many types of test devices. This chapter describes the device requirements and the options for connecting devices with the harness so tests can run and results can be inspected.

This chapter includes the following sections:

• Test Device Requirements
• Test Device Connection Options

---

Test Device Requirements

Test devices must meet these requirements:

• Heap space - At least 128 kilobytes of heap space is required. Some tests require more space.
• MIDlet suite size - A test device must be able to download and install MIDlet suites (test bundles) of at least 75 kilobytes in size. However, most tests are larger. Most can fit in a 128 kilobyte bundle, which is the minimum recommended capacity for a test device. A few tests require bundles of hundreds of kilobytes, and the largest require1,300 kilobytes.
• Record Management Store (RMS) - At least 1024 bytes of free space must be available.

---

Test Device Connection Options

In addition to the requirements listed in Test Device Requirements, a test device must support at least one of the connection options described in this section. The connection options support the transfer of tests and results:

• Tests must be transferred from the harness to a test device so they can run on the device.
• Test results must be transferred from the test device to the harness so they can be incorporated in reports. If the device cannot transfer results, they can be displayed on the device.

Test Bundle Transfer

When a tester directs the harness to run tests, the harness packs groups of tests into MIDP MIDlet suites, which are called test bundles. To run the tests in a bundle, the bundle must be transferred to the test device, installed, and launched. The bundles can be transferred by HTTP or over a local link, such as a serial cable. You specify your choice in the Tests and Bundles section of a template or configuration. The procedures for installing and launching a bundle are device dependent.

HTTP Bundle Transfer

When test bundles are transferred by HTTP, the harness repeatedly creates test bundles and sends them to the Relay. The tester (typically) downloads a bundle from the Relay, installs it and launches it, which causes the tests to run.

The Relay can transfer test bundles over a TCP/IP connection that supports HTTP version 1.0 or 1.1. The device itself does not need to support HTTP over TCP/IP if “bridge” hardware or software between the test device and the Relay can act as an HTTP client on behalf of the device. A WAP gateway is one example of such a bridge. FIGURE 4-1 illustrates HTTP test bundle downloading to a device that supports HTTP over TCP/IP and to a device that requires a bridge.

FIGURE 4-1 Test Bundle Transfer Options - HTTP

Local Link Bundle Transfer

The alternative to HTTP bundle transfer is to use a local link, such as serial, infrared, or Bluetooth. This option requires cooperating software on the harness host, or another host. In the configuration, you specify a directory into which the harness stores the test bundles. You direct the software to download the test bundles from the directory to the test device. FIGURE 4-2 illustrates test bundle transfer by a local link.

FIGURE 4-2 Test Bundle Transfer - Local Link

Test Result Disposition

FIGURE 4-3 illustrates the options for handling test results. For test results to be transferred from a test device to a harness, the test device’s Java environment, or a gateway interposed between the device and the Relay, must support HTTP version 1.0 or 1.1 over TCP/IP. If the test device or gateway does not support HTTP, test results are not sent to the harness. Instead, test results can be displayed on the device. You specify your choice in the Tests and Bundles section of a template or configuration.

FIGURE 4-3 Test Result Disposition Options