OTA Test Description Examples

remote Attribute

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

CODE EXAMPLE 4-8 remote Attribute Entry

<TR>

<TD> <B>remote</B></TD>

<TD> networkAgent: sample.pkg.OTA.OTATest1 -httpServerPort $httpServerPort -testDir $testDir -OTAHandlerClass $OTAHandlerClass

-OTAHandlerArgs $OTAHandlerArgs</TD> </TR>

In the remote attribute, sample.pkg.OTA.OTATest1 is the test class of the server component and all other arguments (-httpServerPort $httpServerPort

-testDir $testDir -OTAHandlerClass $OTAHandlerClass - OTAHandlerArgs $OTAHandlerArgs) are required for OTA tests.

If the test is written for a trusted MIDlet, the argument, -signer=$jks.signer"- signerArgs=$jks.signer.args", must also be included in the remote attribute. This argument is used by the Framework to sign the MIDlet.

The following is an example of the remote attribute entry added to the test description file for an OTA test that is written for a trusted MIDlet.

CODE EXAMPLE 4-9remote Attribute Entry for Trusted MIDlet

<TR>

<TD> <B>remote</B></TD>

<TD> networkAgent: sample.pkg.OTA.OTATest1 -httpServerPort $httpServerPort -testDir $testDir -OTAHandlerClass $OTAHandlerClass

-OTAHandlerArgs $OTAHandlerArgs -signer=$jks.signer "-signerArgs=$jks.signer.args"</TD>

<TR>

The following is an example of a basic OTA test description file.

CODE EXAMPLE 4-10OTA Test Description File

<TITLE>Test Specifications and Descriptions for Test</TITLE> </HEAD>

<BODY>

Chapter 4 Writing Tests 55

Sun Microsystems 1.2 OTA Test Description Examples, Code Example 4-10OTA Test Description File

Models: 1.2

remote Attribute

CODE EXAMPLE 4-9remote Attribute Entry for Trusted MIDlet