An agent is a separate program that works in conjunction with the harness to run tests on the device.

In CDC, the agent is started once, and when started, in a loop, it uses the communication channel to the harness to download the test classes and to execute them on the device, and then reports back the results. In CLDC and MIDP configurations, the execution server supplies the test bundle (it includes the test agent and the tests) and the device’s AMS fetches the bundle and then executes the test agent which in turn executes the bundled tests and reports the results back to the harness.

Tests - Used in CLDC, MIDP, and CDC Automated, Distributed, and OTA test configurations.

The source code and any accompanying information that exercise a particular feature, or part of a feature, of a technology implementation to make sure that the feature complies with the Java specification. A single test can contain multiple test cases. Accompanying information can include test documentation, auxiliary data files, or other resources required by the source code. Tests correspond to assertions of the specification.

Test Types

The developer uses the Framework resources for and organizes the tests based on the test type or testing function (for example, automated tests must be grouped separately from interactive tests because they use different Framework resources). TABLE 1-1presents a simple matrix of the different test configurations and the types of tests that the Framework resources support.

TABLE 1-1Configurations and Supported Test Types

Configuration

Automated Tests

Distributed Tests

Interactive Tests

OTA Tests

 

 

 

 

 

CLDC

Supported

Unsupported

Unsupported

Unsupported

(without MIDP)

 

 

 

 

MIDP

Supported

Supported

Supported

Supported

CDC

Supported

Supported

Supported

Unsupported

 

 

 

 

 

8 Java ME TCK Framework Developer’s Guide • July 2007

Page 28
Image 28
Sun Microsystems 1.2 manual 1Configurations and Supported Test Types