The classes directory generally contains following sub-directories:

classes/preverified - Contains the preverified test classes.

classes/shared/testClasses.lst - The test class dependency file

(testClasses.lst) provides information to the Framework test bundling infrastructure regarding which classes should be bundled for each test.

This information is used in CLDC and MIDP, but ignored in CDC.

doc Directory

The doc directory contains test suite-specific documentation such as User Guides that describe how to run the test suite.

Creating a Test Suite Configuration Interview

All nontrivial test suites require additional information about the tests in order for the test harness to execute them. This additional information, referred to as the test configuration, is obtained from the user through a test suite specific-configuration interview written by the test developer. Additional information about creating configuration interviews for use with the JavaTest harness can be located in Chapter 6 of the JavaTest Architect’s Guide.

The configuration interview consists of a series of questions about the test configuration or specific target implementation, which the user must answer before running tests. The Configuration Editor displays the configuration interview in the harness and exports the user’s answers in a test environment object from which the harness and the Framework can access and obtain the data.

For example, if a test must get the hostName and the portNumber during the test run, the following configuration conditions must be satisfied for the test to run:

The test description file must include an appropriate executeArgs argument.

The following is an example of how executeArgs might be specified in the test description file.

<tr>

<td scope="row"> <b>executeArgs</b> </td> <td> -host $testHost -port $testPort </td> </tr>

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

Page 48
Image 48
Sun Microsystems 1.2 manual Creating a Test Suite Configuration Interview, Doc Directory