# Release Notes ## JavaTest™ Harness Version 3.2.1 #### November 09, 2005

## Table of Contents

Introduction
Changes Since JavaTest Harness, Version 3.1.4
Bugs Fixed in this Release
Known Bugs
Usage Notes
Addendum
  Changes Since JavaTest Harness, Version 2.1.x

## Introduction

The JavaTest harness, Version 3.2.1 release is a maintenance release. It provides the same features of JavaTest harness, Version 3.2. See Bugs Fixed in this Release for a description of the changes in this release.

## Changes Since JavaTest Harness, Version 3.1.4

The JavaTest harness, Version 3.2 release contains basic changes in the following areas:

- New Quick Start Wizard guides users through initial set-up of the GUI.
- Test Manager window updates made to improve usability.
- Configuration editor updates include new option to specify an input file in the configuration (Tests to Run question) that lists the tests to run.
- Configuration editor window provides users the ability to create template configuration (`.jti`) files.
- Configuration editor window provides users the ability to bookmark questions.
- Print function added to configuration Checklist and Question Log dialog boxes.
- Configuration (`.jti`) file checksum requirements have been reduced.
- Filtered Out status tab updated to display the reason why each test is filtered-out.
- Question Log enhanced to show both internal and presentation question (answer) values.
- Report generation updated to include extensive options for producing reports.
- Command-line interface was updated to include new options.
- New verbose command line execution option allows monitoring a test run from the command line.
- Separate user's guides are provided for the GUI, the command-line interface, and the agent.
- Last Test Run view filter added to allow user to see only results from the last or current test run.

### Changes in Agent Command-Line Options

If the agent commands and options are not specified adjacent to each other on the command line, specify the `agentPoolPort` option before the `startAgentPool` option.

Example of previous ordering:
`java -jar javatest.jar ... -startAgentPool -agentPoolPort 1234`

Example of the new ordering:
`java -jar javatest.jar ... -agentPoolPort 1234 ... -startAgentPool`

### Changes in Handling Configuration Question Invalid Input

The JavaTest harness now saves invalid input from the user for configuration questions, instead of completely rejecting the input. Consequently, invalid values provided by the user that were ignored by previous versions of the harness are now rejected by the current version of the harness.

For example, using `yes` as a value on the command line for a Yes/No question was ignored by previous versions of the JavaTest harness. The current version of the JavaTest harness now displays an execution-time configuration error for invalid input from the user.

## Bugs Fixed in this Release

BUG ID | DESCRIPTION
--- | ---
4744381 | Misleading value for tree question response in Question log. In the Question log, if the entire tree was selected, the response was shown as "no response" whereas "all" was more appropriate.
4762952 | Failure to complete an interview "save" is not recorded. For example, if an interview was not saved sucessfully because of file system permissions, the Configuration Editor behaved as though it was saved. Although it displayed the Configuration Editor after the save failed, the JavaTest harness did not indicate that you must save before closing the Configuration Editor.
4801945 | `EditJTI` ignores value of `-classpath` argument. `EditJTI` provides a `-classpath` argument. The value of the argument should be a classpath element that `editJTI` can use to find the interview specified in the `.jti` file. If a user specifies the `-classpath` argument on the command line, `EditJTI` calls a special method to load and edit the interview. `EditJTI` appears to create a new class loader and initialize it with the `classPath` specified by the user. It appears to the user that the `load(inFile, loader)` method should use this new loader to load the interview but it does not. Even if a user specifies the correct classpath for the interview, `EditJTI` may not be able to load the interview.
5064094 | Tests sometimes skipped for execution (Tests to Run). The harness might skip tests for execution when one test name is a substring of another.
5085607 | Question Log doesn't display values of `ChoiceArrayQuestion`.
5102476 | Significant slowdown in `com.sun.javatest.TestFinder`. A significant slowdown in running the JCK for Java SE 1.5 as compared to Java SE 1.4 occured when indexing tests. The algorithm was not optimized for parts of the JCK which had many tests in one folder. JDK 1.5 libraries also have a performance problem doing the string comparison in the TestFinder. Use JDK 1.4.x or JDK 6.0 (when available) to avoid this problem.
6181535 | Names of tests are reverse sorted when they contain hash. Sorting was added to the `TestFinder`, but the default US English comparison reverse sorted strings which differ after a hash character.
6217248 | The `set` command with `-file` option does not work properly in batch mode. If the `set` command with `-file` option is used in a batch file (or as a command line argument) the JavaTest harness returned an error with the message similar to: `xxx.jtb:[line_no]: set: too many arguments`.
6225923 | In Configuration Editor, invoking Save As reverts to old filename. Invoking "Save As ..." and then immediately invoking "Save" changes to the new `.jti` file but then reverts to the original `.jti` file.
6227876 | Restructure docs to emphasize TCK docs over JT docs. The `javatest` documentation directory should be under the `doc/` directory at the same level as the tck_name docs.
6265714 | Batch test execution works incorrectly with existing workdir. If a batch test run uses a test finder other than `BinaryTestFinder` (without the `-tests` option) and is terminated in the middle of the test run, only the previously executed tests are found and executed when the batch tests are run again.

## Known Bugs

The bugs listed in the table below are the known bugs of interest to users that remain to be fixed.

BUG ID | DESCRIPTION
--- | ---
4422418 | Test information not updated while test is running Information in the Test panel status tabs is not updated while a test is running, but is updated when the test is completed. To update the information manually during a test run, switch to a different tab and then return.
4902888 | JavaTest harness crashes when running on Linux 64 bit systems The Virtual Machine for the Java™ platform (Java Virtual Machine or JVM™ machine) crashes when running the JavaTest harness on the Itanium platform. If you are testing such a system, run the tests in an agent configuration, with the harness itself on a different platform.
5002276 | Tests that do not allow interrupts may hang the JavaTest agent The JavaTest harness cannot currently force tests to stop running if they do not allow interrupts.
5018050 | One test timeout can cause consecutive test timeouts when using an agent. If you encounter a series of test timeouts and timeouts which contain the test status message `Timeout waiting for agent to become available`, increasing the agent pool timeout value to a value greater than the basic test timeout (usually 10 minutes) may alleviate the problem. See the online help or the JavaTest harness GUI and CLI User's Guides for additional information.

## Usage Notes

Run JavaTest harness, Version 3.2.1 with Java 2 Standard Edition (J2SE™), Version 1.4.2 or later.

Running the JavaTest harness on Linux Itanium is not supported.

Printing Pages from the Online Help and Test Reports

Because of the method the Java SE platform uses to render fonts, when you print a document from the JavaTest user interface, the fonts in the printed documents are larger than they are when rendered on the screen.

The JavaTest harness User's Guides has been provided in PDF form for you use in printing pages from the documents. While the online help viewer supports printing operations, in some cases you may be unable to use it to print a specific page. If this occurs, use the PDF version of the appropriate User's Guide to print the page.

Changing Status Colors in the GUI

The JavaTest harness allows the user to specify the status colors used in the GUI. See the online help for detailed information about changing the default status colors.

Agent Monitor Tool

The Agent Monitor tool may not apply to all test suites, even if the test suite uses an agent. See your test suite documentation for detailed information about the agent that it uses and its use of the Agent Monitor tool.

# Addendum

For users moving from version 2.1.x to version 3.2.1 of the JavaTest harness, the following section provides a general description of the major differences between the two versions.

## Changes Since JavaTest Harness, Version 2.1.x

The JavaTest harness, version 3.2.1 , adds to and improves both the core version 2.1.x functions and the JavaTest harness GUI. Noticeable changes in the GUI are in the test information panels, the menu bar, and the new Progress Monitor dialog box.

NOTE:
Test suites built for JavaTest harness,version 2.1.x may require modification before the current JavaTest harness can run them. Please contact your technical support representative for more information.

Configuration Editor Window

The JavaTest harness Configuration Editor window replaces the stand-alone JavaTest harness version 2.1.x Configuration Wizard. The Configuration Editor window provides additional features not available in the stand-alone Configuration Wizard. See the online help for detailed information about the JavaTest harness Configuration Editor window.

Online Documentation and Context Sensitive Help

The JavaTest harness includes extensive online documentation and help. The JavaTest harness also allows test suite documentation to be displayed in the GUI. Use the Help menu to display the available online documentation. Press the F1 key to see information about the window that has keyboard focus.

NOTE:
You must establish keyboard focus in a window by highlighting something in it before pressing the F1 key.

Test Manager Window

The Test Manager window replaces both the version 2.1.x Test Panel and Summary Pane. The new Test Manager window has three panes:

- On the left, an expandable tree representation of the test suite
- On the right, information about the test or folder selected in the test tree
- At the bottom, a configurable status display

See the online help for more detailed information.

To start a test run, choose Run Tests -> Start. The configuration editor identifies and collects all configuration information required to run tests.

The JavaTest harness automatically selects the test suite root directory when you open a test suite. You no longer specify the test suite root directory as a parameter.

The JavaTest harness requires that you open or create a work directory before specifying a configuration. The work directory is no longer specified as a parameter.

Providing Configuration Information

Test suites designed to work with the JavaTest harness, version 3.2.1 , use the Configuration Editor window to collect required configuration information in a single configuration file (`.jti`). The JavaTest harness uses the configuration information from the file to run tests. When the user attempts to use an incomplete configuration to run tests, the JavaTest harness opens the Configuration Editor window and prompts the user for the required information. The user can change configuration information any time tests are not running.

Existing test suites can continue to use `.jte` files. Users specify the appropriate `.jte` file in the configuration editor. However, test parameter files (`.jtp`) are no longer supported when running tests in the GUI. These values must be set in the Configuration Editor window. The JavaTest harness incorporates these values with the `.jte` file in a new configuration file (`.jti`).

NOTE:
For compatibility, you can still specify a `.jtp` file from the command line. To see the available command-line options, type the following command at a system prompt:

> `java -jar test_suite/lib/javatest.jar -help`

NOTE:
Include the path of the directory where the `javatest.jar` file is installed (represented as `test_suite` in the example). When the JavaTest harness is bundled with a test suite, the `javatest.jar` file is usually installed in the test suite `lib` directory.

Copyright © 2005 Sun Microsystems, Inc. All rights reserved.
U.S. Government Rights - Commercial software. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements.
Use is subject to license terms. Sun, Sun Microsystems, the Sun logo, Java, and JavaTest are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.
UNIX is a registered trademark in the U.S. and other countries, exclusively licensed through X/Open Company, Ltd.

Copyright © 2005 Sun Microsystems, Inc. Tous droits réservés.
L'utilisation est soumise aux termes du contrat de licence.
Sun, Sun Microsystems, le logo Sun, Java, et JavaTest sont des marques de fabrique ou des marques déposées de Sun Microsystems, Inc. aux Etats-Unis et dans d'autres pays.
UNIX est une marque déposée aux Etats-Unis et dans d'autres pays et licenciée exclusivement par X/Open Company, Ltd.