done at the build time. If the test writer creates a JAR file or a JAD file with special information about the MIDlet suite as part of the bundle, the test writer must also create a manifest file (.mf).

Test Description for OTA Tests

The test description file for OTA tests must contain the ota keyword, the executeClass attribute, and the remote attribute. The test description might also include other attributes such as the remoteSource and executeArgs attributes. See “OTA Test Description Examples” on page 55 for examples of complete test description files.

Required OTA Test Keyword

The ota keyword identifies the type of test to the harness and enables test selection by the user. If more than one keyword is specified, the names must be separated by white space. The following is an example of the ota keyword entry that must be added to the test description file.

CODE EXAMPLE 4-6Required OTA Test Keyword

<TR>

<TD> <B>keywords</B></TD> <TD> ota </TD>

</TR>

executeClass Attribute

The executeClass attribute specifies the client test class, while the remote attribute specifies the execution command for the server test component. The following is an example of the executeClass attribute entry that must be added to the test description file.

CODE EXAMPLE 4-7 executeClass Attribute Entry

<TR>

<TD> <B>executeClass</B></TD>

<TD> sample.pkg.OTA.Test_MIDlet</TD> </TR>

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

Page 74
Image 74
Sun Microsystems 1.2 manual Test Description for OTA Tests, Code Example 4-6Required OTA Test Keyword