Glossary

.jtb Files

See command file.

.jte Files

See environment files.

.jti Files

See configuration file.

.jtp Files

See parameter files.

.jtr File

See test result files.

.jtx Files

See exclude list.

A

Audit

The JavaTest harness includes an audit tool that you can use to analyze the test results in a work directory. The audit tool verifies that all tests in a test suite ran correctly and identifies any audit categories of a test run that had errors.

You can use the GUI or the command-line interface to audit a test run.

B

Batch Mode

You can use either the -batch mode option or the current -run command to run tests from the command line or as part of a build process. Unless you are running tests from the command line and are using the GUI to monitor the test run, the -batch mode option is no longer required.

C

Class

The prototype for an object in an object-oriented language. A class might also be considered a set of objects that share a common structure and behavior. The structure of a class is determined by the class variables that represent the state of an object of that class and the behavior is given by a set of methods associated with the class.

Command File

You can place routinely used configuration settings in a command file and include it in a command line. The command file is an ASCII file containing a lengthy series of commands and their arguments used in the command-line interface to modify specific configuration values before running tests.

You can use command files to configure and run tests, write test reports, and audit test results either from the command line or as a part of a product build process. Using a command file allows you to repeatedly use a configuration without retyping the commands each time a test run is performed.

It is recommended that a descriptive name and the extension .jtb are used to help identify the function of each command file.

Configuration

Information about the computing environment required to execute a test suite.

In the GUI, you can use the Configuration Editor to collect or modify configuration information or to load an existing configuration. See Configuration Editor. The Configuration Editor collects the following two types of data in an configuration file:

In the command-line interface, you can perform the following tasks:

Configuration File

Contains all of the information collected by the configuration editor about the test platform.

The JavaTest harness derives the configuration values required to execute the test suite from environment entries in a configuration file (.jti).

Use the Configuration Editor or EditJTI to change configuration values in a .jti file.

You can also set specific values in the command line.

Configuration Value

A value specified by the user for the purpose of configuring a test run.

Configuration values are derived from environment entries in a configuration file and used by test suite specific plugin code to execute and run tests.

For test suites prior to the JavaTest harness, version 3.0, the configuration value is read from an environment file (.jte).

For JavaTest harness, version 3.0 (or later) test suites, the configuration value is derived from the configuration file (.jti).

Use the Configuration Editor or EditJTI to change the configuration values in the .jti file.

You can also set specific configuration values in the command line.

Current Configuration

The configuration containing the test environment and standard values currently loaded in the test manager or specified in the command line for use in running tests and displaying test status.

D

E

EditJTI

The JavaTest harness provides an EditJTI utility that you can use from the command line to edit the values entered in a configuration file without opening the JavaTest GUI. The EditJTI utility is the batch command equivalent of the JavaTest Configuration Editor.

Environment

See Test Environment.

Environment Entry

A name-value pair derived from a configuration file and used by test suite specific plugin code to execute and run tests. These name-value pairs provide information (configuration values) about how to run tests of a test suite on a particular platform.

For test suites prior to the JavaTest harness, version 3.0, the name-value pairs are read from an environment file (.jte).

For JavaTest harness, version 3.0 (or later) test suites, the name-value pairs are derived from the configuration file (.jti).

Environment Files

Contain one or more test environments used by test suites prior to the JavaTest harness version 3.0. Environment files are identified by the .jte extension in the file name.

Error

The test is not filtered out and the JavaTest harness could not execute it. There are no test results for tests having errors. Errors usually occur because the test environment is not properly configured.

In the GUI, the JavaTest harness displays error icons for tests with errors and for folders containing any tests with errors. Folders marked with error icons can also contain tests and folders that are Failed, Not Run, Passed, and Filtered out.

Exclude List

Exclude list files (*.jtx), supply a list of invalid tests to be filtered out of a test run by the test harness. The exclude list provides a level playing field for all implementors by ensuring that when a test is determined to be invalid, then no implementation is required to pass it. Exclude lists are maintained by the technology specification Maintenance Lead and are made available to all technology licensees.

In the GUI, use the configuration editor to add or remove exclude lists from a test run. In the command line, you can specify an exclude list in the command.

To view the contents of an exclude list, choose Configure -> Show Exclude List from the Test Manager menu bar. Exclude lists can only be edited or modified by the test suite Maintenance Lead.

F

Fail

Test results determined by the JavaTest harness that do not meet passing criteria.

In the GUI, the JavaTest harness displays Failed icons for tests that the test suite has determined have failing results and for folders containing any tests with fail results. Folders marked with Failed icons can also contain tests and folders that are Not Run, Passed, and Filtered out.

Filtered Out

Folders and their tests that are excluded from the test run by one or more test run filters.

In the GUI, Filtered Out folders and tests are identified in the test tree by grey Gray folder icon folder and Gray test icon test icons.

Filters

A facility in the JavaTest harness that accepts or rejects tests based on a set of criteria. There are two types of filters in the JavaTest harness, view filters and run filters. View filters are set in the Test Manager to display the results for specific folders and tests and to create test reports. Run filters are set in the Configuration Editor or are specified as commands in the command-line to specify which tests are run.

G

H

HTTP Server

Software included in the JavaTest harness that services HTTP requests used to monitor a test run from a remote work station.

I

Interview File

See configuration file.

J

JTI

Standard file extension for a configuration file. See configuration file.

K

Keywords

Special values in a test description that describe how the test is executed.

Keywords are provided by the test suite for use in the Configuration Editor or command line as a filter to exclude or include tests in a test run.

L

M

Multiple Document Interface

A window style in which the JavaTest harness desktop is a single top-level window that contains all JavaTest harness windows opened to perform a task.

Use the Preferences dialog box to select the MDI window style. See JavaTest Harness Preferences.

N

O

Observer

An optional class instantiated from the command line to observe a test run. The class implements a specific observer interface.

P

Parameter Files

Files used prior to the JavaTest harness, version 3.0, to configure how the JavaTest harness runs the tests on your system. Parameter files have the file name extension of .jtp.

Use of parameter files is deprecated, however, the JavaTest harness provides support for those test suites that use parameter files.

Pass

Test results determined by the JavaTest harness to meet passing criteria.

The JavaTest harness displays Passed icons for tests that the test suite has determined have passing results and for folders containing only tests with passing results.

Port Number

A number assigned to the JavaTest harness that is used to link specific incoming data to an appropriate service.

Prior Status

A filter used to restrict the set of tests in a test run based on the last test result information stored in the test result files (.jtr) in the work directory.

Use the configuration editor or command line to enable the Prior Status filter for a test run.

Q

R

Report Directory

The directory in which the JavaTest harness writes test reports.

The location of the report directory is set in the GUI or from the command line by the user when generating test reports.

S

Standard Values

The Quick Set mode of the Configuration Editor displays the standard values of a configuraion.

System Properties

Contains environment variables from your system that are required to run the tests of a test suite.

Because the JavaTest harness cannot directly access environment variables, you must use command-line options to copy them into the JavaTest harness system properties.

T

Test Description

Machine readable information that describes a test to the JavaTest harness so that it can correctly process and run the related test. The actual form and type of test description depends on the attributes of the test suite. When using the JavaTest harness, the test description is a set of test-suite-specific name-values pairs.

Each test in a test suite has a corresponding test description that is typically contained in an HTML file.

Test Environment

A collection of configuration values derived from environment entries in the configuration file that provide information used by test suite specific plugin code about how to execute and run each test on a particular platform.

When a test in a test suite is run, the JavaTest harness gives the script a test environment containing environment entries from configuration data collected by the configuration editor. See configuration.

Prior to the JavaTest harness, version 3.0, the environment entries were read from an environment file. Use of environment files is deprecated. However, the JavaTest harness continues to provide support for those test suites that use environment files. See environment file.

Test Manager

The JavaTest harness window used to configure, run, monitor, and manage tests from its panels, menus, and controls.

The Test Manager window is divided into two panes. It displays the folders and tests of a test suite in the tree pane on the left and provides information about the selected test or folder in the information panes on the right.

A new Test Manager window is used for each test suite that is opened.

Test Result Files

Contains all of the information gathered by the JavaTest harness during a test run.

The test result files (.jtr) are stored in a cache in the work directory associated with the test suite.

You can view the test result files in a web browser configured to use the JavaTest harness ResultBrowser servlet.

Test Run Filters

Include or exclude tests in a test run. Tests are included or excluded from test runs by the following means:

Test run filters are set using the Configuration Editor or the command-line interface.

Test Script

A script used by the JavaTest harness, responsible for running the tests and returning the status (pass, fail, error) to the harness. The test script must interpret the test description information returned to it by the test finder. The test script is a plug-in provided by the test suite. In the GUI, the Test Manager Properties dialog box lists the plug-ins that are provided by the test suite.

Test Suite

A collection of tests, used in conjunction with the JavaTest harness, to verify compliance of the licensee's implementation of the technology specifications.

A test suite must be associated with a work directory before the JavaTest harness can run its tests.

U

V

W

Work Directory

A directory associated with a specific test suite and used by the JavaTest harness to store files containing information about the test suite and its tests.

Until a test suite is associated with a work directory, the JavaTest harness cannot run tests.

X

Y

Z