4.Test Name - The execution server returns the name of the next test in the application bundle that the AMS should run.

While the tests from the application bundle are loaded onto the device by the AMS, the execution server establishes the sequence in which the tests in the bundle are run.

5.Check or Send Message - The test sends either a message or a check message request to the Framework messaging service on the harness.

6.Get Message - The Framework messaging service on the harness sends the test a get message command.

7.Check or Send Message - The server-side test sends either a message or a check message request to the Framework messaging service on the harness.

8.Get Message - The Framework messaging service on the harness sends the server-side test a get message command.

9.Request an Action- The Framework messaging service sends a message request to the user that requires an action on a test.

10.Action - The user performs the action on the test requested by the messaging service.

11.sendTestResult - The agent returns the test results to the harness.

The agent repeats items 3, 4, and 5 until all tests in the application bundle are run. When all tests in the application bundle are run, the AMS requests the next application bundle (items 1 and 2) and the sequence is repeated until all tests and all test bundles in the test suite are run.

Example of an Interactive Test

Examples of interactive tests can be viewed (and executed) in the AdvancedTestSuite directory of the Framework bundle.

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

Page 72
Image 72
Sun Microsystems 1.2 manual Example of an Interactive Test