Release NotesJavaTest™ Harness
|
The JavaTest harness, Version 3.2.2_01 release is a patch release and contains only minor fixes beyond the 3.2.2. 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.
The JavaTest harness, Version 3.2 release contains basic changes in the following areas:
.jti
) files..jti
) file checksum requirements have been reduced.
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
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.
BUG ID | DESCRIPTION |
---|---|
4720256 |
Poor layout if ChoiceQuestion has long strings as choices
The rendering exceeds the default horizontal space in the center Configuration Editor panel. |
4749843 |
Poor layout if ChoiceArrayQuestion has many options
The rendering produces a 2x4 grid, which exceeds the horizontal width of the default Configuration Editor, and no scrollbar is provided. |
6210307 |
com.sun.javatest.agent.Agent.close() is invalid
If test execution is stopped in the middle of the test run, JavaTest prints out a NullPointerException into stderr. SocketExceptions are also printed into stderr when the test run is finished, because of user action or because all tests are finished. |
6246636 |
Info printed to log and ref is not flushed if MultiTest is interrupted
The log (or ref) is flushed only if all the tests are finished. If the process is interrupted, information from ref and log PrintWriters is not printed. |
6320091 |
com.sun.javatest.lib.MultiStatus doesn't get the first test case failure
|
6360959 |
config.html with 'incomplete last line' when generated on commandline (batch mode)
Using the command line tool instead of the GUI to generate a report can cause the |
6410572 |
JavaTest produces incorreclty-formed HTML report (config.html)
Choices are not correctly rendered in the configuration HTML report. |
6432954 |
Possible deadlock when multiple threads write to a test result.
Deadlock could occur if multiple threads update a test result at the same time. |
6447226 |
Select-All should be enabled for ChoiceArrayQuestion in the interview
The standard keystroke Control-a now acts as a select-all operation in configuration questions which have multiple possible choices (checkboxes). |
6450321 |
Clear Results fails when all nodes in tree are selected (ArrayIndexOutOfBoundsException)
An exception was generated and the operation was not performed. |
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 |
Run JavaTest harness, Version 3.2.2_01 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.
For users moving from version 2.1.x to version 3.2.2_01 of the JavaTest harness, the following section provides a general description of the major differences between the two versions.
The JavaTest harness, version 3.2.2_01 , 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:
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.2_01 ,
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 © 2006 Sun Microsystems, Inc. All rights reserved.
Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S. and in other countries.
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 harness 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 © 2006 Sun Microsystems, Inc. Tous droits réservés.
Sun Microsystems, Inc. détient les droits de propriété intellectuels relatifs à la technologie incorporée dans le produit qui est décrit dans ce document. En particulier, et ce sans limitation, ces droits de propriété intellectuelle peuvent inclure un ou plus des brevets américains listés à l'adresse http://www.sun.com/patents et un ou les brevets supplémentaires ou les applications de brevet en attente aux Etats - Unis et dans les autres pays.
L'utilisation est soumise aux termes du contrat de licence.
Sun, Sun Microsystems, le logo Sun, Java et JavaTest harness 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.