C H A P T E R 3

User's Guide

Installing the Multitasking Quality Test Suite adds multitasking tests to those already built into the Java Device Test Suite. You select and run the tests in these suites exactly as described in the Sun Java Device Test Suite User's Guide.

Using the Test Console

Use the Test Console as described in the Sun Java Device Test Suite User's Guide. Click on Multitasking Quality Test Suite to display a list of MT tests. The Summary tab shows the results of the tests that you run, as shown in FIGURE 3-1.

FIGURE 3-1 Multitasking Quality Test Suite Summary Window and Test List

Multitasking Quality Test Suite Summary Window [ D ]

The Multitasking Quality Test Suite provides tests for the following technologies, as shown in TABLE 3-1.

TABLE 3-1 Multitasking Quality Test Suite Tests
Test Suite	Description
app_manager	Tests Application Manager functionality and behavior.
chapi	Tests Content Manager API (JSR 211) functionality and behavior.
fg_bg_switch	Tests the switching of applications between foreground and background.
media	Tests Mobile Media API (JSR 135), including audio capturing, media controls, general multitasking, and video playback.
papi	Tests Payment API (JSR 229) functionality and behavior.
preemption	Tests multitasking preemption.
push	Tests push functionality and behavior.
resource_policy	Tests multitasking resource policy, including fixed partition and open for competition resource management.
robustness	Tests robustness and stability.
start_stop	Tests starting and stopping of MIDlet suites.
svg	Tests Scalable 2D Vector Graphics API (JSR 226) functionality and behavior.

Configuring the Multitasking Quality Test Suite

The Java Device Test Suite provides a Configuration Editor for configuring the properties of the tests you run. The Multitasking Quality Test Suite has eight categories of tests that can be configured, as shown in FIGURE 3-2.

FIGURE 3-2 Configuration Editor Showing Multitasking Quality Test Suite Properties

Configuration Editor Window [ D ]

The Multitasking Quality Test Suite enables you to configure the following properties, as shown inTABLE 3-2.

TABLE 3-2 Multitasking Quality Test Suite Properties
Property	Description
Datagram Resource Policy	Properties for configuring the sending and receiving of test messages using datagrams.
Open Policy	Properties for configuring open for competition access to multitasking resources.
Send Push Message	Properties for configuring the sending of push messages.
General	General information about Java Device Test Suite.
Installation/Deletion Status Reports	Information about Java Device Test Suite management.
Socket Resource Policy	Properties for configuring the sending and receiving of test messages using sockets.
Fixed Policy	Properties for configuring fixed size allocation access to multitasking resources.
Receive Push Message	Properties for configuring the reception of push messages.

Configuring Resource Policy Tests

A system administrator can choose from various resource management policies.

The following sections provide information about fixed and open policy settings. For more information about the distinctions between fixed and open multitasking policies, see the Sun Java Wireless Client Multitasking Guide.

Configuring Datagram Resource Policy Properties

Using the Java Device Test Suite Configuration Editor, you can configure the datagram resource policy properties, as shown in FIGURE 3-3.

FIGURE 3-3 Configurable Datagram Resource Policy Properties

Datagram Resource Policy Form [ D ]

The configurable datagram properties shown in TABLE 3-3 are used by both fixed and open policies. You must configure these properties for your device.

TABLE 3-3 Datagram Resource Policy Properties
Property Name	Description	Default Value
`UDP_PORT_START_1`	Starting port number from where all Datagram sockets are created	6000
`UDP_PORT_START_2`	Starting port number from where all Datagram sockets are created	5501

Configuring Socket Resource Policy Properties

Using the Java Device Test Suite Configuration Editor, you can configure the socket resource policy properties, as shown in FIGURE 3-4.

FIGURE 3-4 Configurable Socket Resource Policy Properties

Socket Resource Policy Form [ D ]

The socket resource policy properties in TABLE 3-4 are used by both fixed and open policies. You must configure these properties for your device.

TABLE 3-4 Socket Resource Policy Properties
Property Name	Description	Default Value
`TCP_PORT_START_1`	Starting port number from where all server sockets are created or client socket is opened	8900
`TCP_PORT_START_2`	Starting port number from where all server sockets are created or client socket are opened	4501
`RP_SOCKET_IP`	IP address of the device for client socket connections	device-IP

Tests That Require Fixed or Open Policy Settings

Test cases in other sections that require the user to set Fixed Policy or Open Policy properties include the following:

Starting and Stopping MIDlets:

com.sun.mt.push.uc_04#tc_01_01

com.sun.mt.push.uc_04#tc_01_02

com.sun.mt.push.uc_04#tc_01_03

com.sun.mt.push.uc_23#tc_01_01

com.sun.mt.push.uc_23#tc_01_02

com.sun.mt.push.uc_23#tc_01_03

Foreground and Background:

com.sun.mt.push.uc_02#tc_05_01

com.sun.mt.push.uc_02#tc_05_02

com.sun.mt.push.uc_02#tc_05_03

Setting Open Policy Configurations

If the software on your device is configured to use an open policy, choose the Open Policy tab and set each of the properties to the values appropriate for your device, as shown in FIGURE 3-5.

FIGURE 3-5 Configurable Open Policy Properties

Open Policy Form [ D ]

The following properties must be configured for an open policy configuration, as shown in TABLE 3-5.

TABLE 3-5 Open Policy Properties
Property Name	Description	Default Value
`MEMORY_RES_O`	Default MIDlet suite memory reserved (`SUITE_MEMORY_RESERVED`)	`100`
`TCP_O_G`	Global resource limit for TCP client sockets (`TCP_CLI_GLOBAL_LIMIT`)	`16`
`TCP_O_A`	AMS reserve resource limit for TCP client sockets (`TCP_CLI_AMS_RESERVED`)	`2`
`TCPS_O_G`	Global resource limit for TCP server sockets (`TCP_SER_GLOBAL_LIMIT`)	`12`
`TCPS_O_A`	AMS reserve resource limit for TCP server sockets (`TCP_SER_O_AMS_RESERVED`)	`0`
`UDP_O_G`	Global resource limit for UDP sockets (`UDP_GLOBAL_LIMIT`)	`12`
`UDP_O_A`	AMS reserve resource limit for UDP sockets (`UDP_AMS_RESERVED`)	`0`
`IMG_M_O_G`	Global resource limit for mutable images (`IMAGE_MUT_GLOBAL_LIMIT`)	`1200000`
`IMG_M_O_A`	AMS reserve resource limit for mutable images (`IMAGE_MUT_AMS_RESERVED`)	`200000`
`IMG_I_O_G`	Global resource limit for immutable images	`1300000`
`IMG_I_O_A`	AMS reserve resource limit for immutable images (`IMAGE_IMMUT_AMS_RESERVED`)	`70000`

Note - The following Open Policy tests work only on the Linux platform with builds using QT graphics and Adaptive User Interface Technology, and must be excluded if you run on the Win32 platform or use non-QT builds on Linux:
com.sun.mt.resource_policy.open.uc_51#tc_02_04 com.sun.mt.resource_policy.open.uc_51#tc_02_05 com.sun.mt.resource_policy.open.uc_51#tc_03_04 com.sun.mt.resource_policy.open.uc_51#tc_03_05 com.sun.mt.resource_policy.open.uc_51#tc_04_04 com.sun.mt.resource_policy.open.uc_51#tc_04_05For more information on how to exclude tests, see the Sun Java Device Test Suite Administrator's Guide.

Setting Fixed Policy Configurations

If the software on your device is configured to use a fixed policy, choose the Fixed Policy tab and set each of the properties to the values appropriate for your device, as shown in FIGURE 3-6.

FIGURE 3-6 Configurable Fixed Policy Properties

Fixed Policy Form [ D ]

The following properties must be configured for an fixed policy configuration, as shown in TABLE 3-6.

TABLE 3-6 Fixed Policy Properties
Property Name	Description	Default Value
`UDP_A`	AMS reserve resource limit for UDP sockets (`UDP_AMS_RESERVED`)	`4`
`UDP_G`	Global resource limit for UDP sockets (`UDP_GLOBAL_LIMIT`)	`16`
`UDP_S`	Per-suite resource limit for UDP sockets (`UDP`_`SUITE_RESERVED` has the same value as `UDP_SUITE_LIMIT`)	`4`
`TCP_G`	Global resource limit for TCP client sockets (`TCP_CLI_GLOBAL_LIMIT`)	`48`
`TCP_A`	AMS reserve resource limit for TCP client sockets (`TCP_CLI_AMS_RESERVED`)	`12`
`TCP_S`	Per-suite resource limit for TCP client sockets (`TCP_CLI_SUITE_RESERVED` has the same value as `TCP_CLI_SUITE_LIMIT`)	`12`
`TCPS_G`	Global resource limit for TCP server sockets `TCP_SER_GLOBAL_LIMIT`)	`16`
`TCPS_A`	Per- suite resource limit for TCP server sockets (`TCP_SER_AMS_RESERVED`)	`4`
`TCPS_S`	Per-suite resource limit for TCP server sockets (`TCP_SER_SUITE_RESERVED` has the same value as `TCP_SER_SUITE_LIMIT`)	`4`
`IMG_M_S`	Per-suite resource limit for mutable images	`800000`
`IMG_I_S`	Per-suite resource limit for immutable images	`800000`
`IMG_M_G`	Global resource limit for mutable images	`3600000`
`IMG_M_A`	AMS reserve resource limit for mutable images	`1200000`
`IMG_I_G`	Global resource limit for immutable images	`1300000`
`IMG_I_A`	AMS reserve resource limit for immutable images	`1200000`
`MEMORY_RES`	Default MIDlet suite memory reserved	`900`
`ISOLATES`	Maximum number of isolates (`MAX_ISOLATES`)	`4`

Note - The following Fixed Policy tests work only on the Linux platform with builds using QT graphics and Adaptive User Interface Technology, and must be excluded if you run on the Win32 platform or use non-QT builds on Linux:
com.sun.mt.resource_policy.fixed.uc_18#tc_02_04 com.sun.mt.resource_policy.fixed.uc_18#tc_02_05For more information on how to exclude tests, see the Sun Java Device Test Suite Administrator's Guide.

Configuring the `sendMSG` MIDlet

The Multitasking Quality Test Suite sendMSG MIDlet is used like any other Partner MIDlet in the Java Device Test Suite. For more information on Partner MIDlets, see the Java Device Test Suite Test Notes.

Two kinds of Multitasking QTS tests require you to run MIDlets on two devices:

Push Socket Message tests

Push Datagram Message tests

Note - When running these tests, make Device A the device being tested and Device B the device that runs the sendMSG MIDlet.

Both Push Socket and Push Datagram tests are configured using the Send Push Message Property form, as shown in FIGURE 3-7.

FIGURE 3-7 Configurable SendPush Message Properties

Send Push Message Form [ D ]

Receiving Push Message Tests

The property MIDlet-Push-1 for Receiving Push Messages is common to both socket and datagram tests. Run Socket Receive Push Message tests in their own session. Then change the value of MIDlet-Push-1 to be datagram://port-number and run a new session for the Datagram Receive Push Message tests.

The MIDlet-Push-1 property setting is configured in the Receive Push Message Property form, as shown in FIGURE 3-8.

FIGURE 3-8 Configurable Receive Push Message Property

Receive Push Message Form [ D ]

Push Socket Message Tests

The following tests send Push Messages using sockets:

com.sun.mt.push.uc_05a#tc_01_01

com.sun.mt.push.uc_05a#tc_02_01

com.sun.mt.push.uc_06a#tc_01_01

com.sun.mt.push.uc_06a#tc_02_01

com.sun.mt.push.uc_06b#tc_01_01

com.sun.mt.push.uc_06c#tc_01_01

com.sun.mt.push.uc_06c#tc_02_01

com.sun.mt.push.uc_08#tc_01_01

Test cases in other sections that use Push Socket Message tests:

com.sun.mt.app_manager.uc_02_5#tc_05

com.sun.mt.app_manager.uc_25#tc_01

com.sun.mt.preemption.uc_54#tc_02

Sending Push Socket Message Tests

1. Select the Send Push Message tab.

2. Set SEND_PUSH_DEVICE_IP to the IP address of Device A.

3. Set SEND_PUSH_SOCKET_PORT_1 to the port number on Device A.

The default value is 5432.

The sendMSG MIDlet sends the message to this port when you click the SendOne button.

4. Set SEND_PUSH_SOCKET_PORT_2 to another port number on Device A.

The default value is 5433.

The sendMSG MIDlet sends the message to this port (and to the port specified in SEND_PUSH_SOCKET_PORT_1) when you click the SendTwo button.

Note - Do not set SEND_PUSH_SOCKET_PORT_1 and SEND_PUSH_SOCKET_PORT_2 to the same port number.

5. Set SEND_PUSH_MSG to be the message you want sent.

The default value is testMSG.

Receiving Push Socket Message Tests

1. Select the Receive Push Message tab.

2. Set MIDlet-Push-1 to the Java Application Descriptor (JAD) configuration file used for auto launching.

The default value is socket://:5432.

This value must be specified in the following format:

socket://:port-number

Note - You must set port-number to be the same port you specified for SEND_PUSH_SOCKET_PORT_1.

Push Datagram Message Tests

The following tests send Push Messages using datagrams:

com.sun.mt.push.uc_05a#tc_01_02

com.sun.mt.push.uc_05a#tc_02_02

com.sun.mt.push.uc_06a#tc_01_02

com.sun.mt.push.uc_06a#tc_02_02

com.sun.mt.push.uc_06b#tc_04

com.sun.mt.push.uc_06b#tc_01_02

com.sun.mt.push.uc_06c#tc_01_02

com.sun.mt.push.uc_06c#tc_02_02

com.sun.mt.push.uc_08#tc_01_02

Sending Push Datagram Message Tests

1. Select the Send Push Message tab.

2. Set SEND_PUSH_DEVICE_IP to the IP address of Device A.

3. Set SEND_PUSH_DATAGRAM_PORT_1 to the port number on Device A.

The default value is 5434.

The sendMSG MIDlet sends the message to this port when you click the SendOne button.

4. Set SEND_PUSH_DATAGRAM_PORT_2 to another port number on Device A.

The default value is 5435.

The sendMSG MIDlet sends the message to this port (and to the port specified in SEND_PUSH_DATAGRAM_PORT_1) when you click the SendTwo button.

Note - Do not set SEND_PUSH_DATAGRAM_PORT_1 and SEND_PUSH_DATAGRAM_PORT_2 to the same port number.

5. Set SEND_PUSH_MSG to be the message you want sent.

The default value is testMSG.

Receiving Push Datagram Message Tests

1. Select the Receive Push Message tab.

2. Set MIDlet-Push-1 to the JAD configuration file used for auto launching.

The default value is socket://:5432.

This value must be set to datagram and specified in the following format:

datagram://:port-number

Note - You must set port-number to be the same datagram you specified for SEND_PUSH_DATAGRAM_PORT_1.

Tests Requiring Certificate Setup

Certain Push Socket and Datagram Message tests require you to provide a signed certificate for the Push Application, so the tests can check if the system is able to decide automatically to launch the Push Application. For the Push Application to be properly launched, it must be signed and included in the trusted security domain.

The same applies to Media tests performing audio capturing: for the Media Application to be able to access the restricted javax.microedition.media.control.RecordControl API, it must be signed and included in the trusted security domain.

The following tests require the signed certificate:

com.sun.mt.push.uc_06b#tc_01_01

com.sun.mt.push.uc_06b#tc_01_02

com.sun.mt.media.policy_B.capture.uc_m51

com.sun.mt.media.policy_B.capture.uc_m52

com.sun.mt.media.policy_B.capture.uc_m53

com.sun.mt.media.policy_B.capture.uc_m54

com.sun.mt.media.policy_B.capture.uc_m55

com.sun.mt.media.policy_B.capture.uc_m56

com.sun.mt.media.policy_B.capture.uc_m57

Setting Up the Signed Certificate

1. Import the signature file keystore.ks into the Java Wireless Client software client keystore, _main.ks.

The keystore.ks file is located in the following directory:

$ROOT_DIR/admin/shared/testpacks/Multitasking_Quality_Test_Suite/src/client/com/sun/mt/push

In the above path, $ROOT_DIR is the root of the Java Device Test Suite installation.

2. To import the keystore.ks file, go to the Java Wireless Client Software directory and use the MEKeyTool with the following command and flags:

% java -jar bin/MEKeyTool.jar -import -MEKeystore appdb/_main.ks -keystore $ROOT_DIR/admin/shared/testpacks/Multitasking_Quality_Test_Suite/src/client/com/sun/mt/push/keystore.ks -storepass password -aliaspush -domain operator

For more information on the MEKeyTool utility, see Sun Java Wireless Client Tools Guide.