Chapter 7. Glossary
Prev |  |

# Chapter 7. Glossary

Action

  A method which is carried out on a Component. An Action is part of a Test Step, and serves to either execute a command (e.g. click, enter text), or verify property or state information about a Component (e.g. check Component name, check visibility).

AUT

  The Application Under Test. The AUT is the entire program that you wish to test.

AUT Conﬁguration

  The information required in order to locate and start an AUT in the conﬁguration desired by the user. An AUT Conﬁguration includes program information such as JRE location and class path, and AUT conﬁguration information such as command-line parameters and environment variables. Details about the AUT are given when a project is created, and are entered into the relevant ﬁelds in the Test Suite Editor.

CAP

  The three parts of a Test Step : Component, Action, Parameter.

Classname for AUT

  The fully qualiﬁed classname which contains the main method of the AUT.

Classpath for AUT

  An environment variable that informs Java where to look for the class ﬁles which are needed to run the AUT.

Component

  A user interface object. Each component has a set of actions that can be carried out upon it.

Component Name

  The symbolic name you choose for a component in the AUT and use in a Test Step or Test Case.

Component Names View

  In this view, component names in reused Test Cases can be reassigned to create multiple component names for one Test Step. This allows many components of the same type or within the same group or family to be mapped to the same Test Step. The default position of the Component Names View is in the lower right-hand corner of the perspective.

Component Type

  The type of graphical user interface object which will be acted upon in a Test Step, e.g. ”Menu Bar” or ”Combo Box”.

Data Sets View

  The view in which multiple parameter values for a Test Case can be deﬁned and edited. The default position of the Data Sets View is the right-hand side of the perspective, in the middle.

Empty string

  To enter an empty string as a parameter (i.e. nothing at all), use backslash \.
  To actually write a backslash, you must enter two backslashes.

Escape character

  The character used to cancel any special function that the following symbol may have. The default escape character is \.

Event Handling

  The process by which errors are dealt with during the execution of a test. If no user-deﬁned Event Handler has been speciﬁed, a default Event Handler is activated.

Graphical User Interface

  A means of interacting with a computer by the use of a graphically oriented (as opposed to text-oriented) display. Modern graphical user interfaces (GUI’s) are controlled by a mouse as well as a keyboard, and consist of windows, buttons, text areas, and other manipulable objects which are designed to make computer operation simpler and more intuitive.

ITE

  Short for Integrated Test Environment. By this we mean the application where tests are written.

JAR

  The Java™Archive ﬁle format. It allows multiple classes and other program ﬁles and data to be combined into one compressed ﬁle, which often represents a complete program. In this context, a JAR describes the Java™Archive of the AUT.

Object mapping

  The process by which component names you created in your test are attached to the technical names used in the AUT.

Parameters

  The information that is given to an action to perform a Test Step, such as name, value, etc. A parameter consists of:

  - a name

  - a type

  - a value

  Most actions require one or more parameters.

Parameter Name

  A name which describes a parameter which is sent to an action.

Parameter Type

  The type of value which is sent as a parameter to an action. The following parameter types are supported:

  - String

  - Integer

  - Boolean

Parameter Value

  The contents of the parameter which is sent to an action. A parameter value can either be a static value (e.g. Hello, 123), a reference (e.g. =REFERENCE) or a variable.

Port Number

  A software address used to identify and communicate between individual programs or services on a single computer or between multiple computers on a network. A hostname and port number must be given in order to connect to an AUT Agent.

Project

  A Project contains all the information for the test, including Test Suites and Test Cases, AUT’s and data. Projects are stored in the database.

Project Properties

  Information pertaining to the active project, including the name (all projects in the database must have unique names).

Propagation

  When references are entered, the parameter they replace is carried up into the next Test Case in the hierarchy. This is propagation.

Properties View

  The view for displaying and editing the properties of selected Test Steps or Test Cases, located by default in the top right-hand corner of the perspective. Test Steps and Test Cases can be edited in the Properties View by clicking on their icon in their respective editor. The Properties View is also used to display detailed results of a Test Suite once it has been executed.

Reference Symbol

  The character used to denote a reference within a parameter. The default reference symbol is =.

Speciﬁcation

  The method by which test details and instructions are entered by the user in the ITE. Tests are not programmed, but rather speciﬁed in plain language, then object-mapped to the program’s technical names.

Step Delay

  The time to wait between Test Steps, given in milliseconds. A step delay causes a slower test execution.

Technical Name

  A name given to a graphical user interface object of an AUT by a software developer. Technical names are used to uniquely identify an object within an application and are mapped to a component name as deﬁned by the user in a Test Step.

Test Case

  A reusable test object which contains Test Steps or other Test Cases.

Test Case Browser

  A view which shows the hierarchy of Test Cases as entered and deﬁned by the user. The Test Case Browser is by default in the bottom left-hand corner of the perspective.

Test Case Editor

  An editor area used to create and alter Test Cases and Test Steps. The Test Case Editor is located by default in the center of the perspective.

Test Data

  Values which are entered into parameters for an action in Test Steps. Test data may be entered directly into a parameter or referenced.

Test Job

  A Test Job is a collection of Test Suites which are designed to be executed after each other. The Test Suites can test the samme AUT, different instances of the same AUT, or different AUT’s entirely.

Test Result View

  The view which displays the results of an executed Test Suite.

Test Result View

  The view which displays the results of an executed Test Suite.

Test Step

  The smallest test object. A Test Step belongs to a Test Case. A Test Step consists of

  - a Component

  - an Action

  - a Parameter

Test Suite

  A Test Suite uses an AUT conﬁguration and contains all Test Cases and their respective Test Steps, in the order in which they are to be tested.

Test Suite Browser

  The view containing the Test Suite tree, where the Test Cases in a Test Suite can be seen. The Test Suite Browser is situated by default in the top left-hand corner of the perspective.

Test Suite Editor

  An editor pane used to view the properties of the Test Suite and the Test Cases used in it, and to edit their parameter values and names. The Test Suite Editor is located by default in the center of the perspective.

Workspace

  Personal preferences relating to the client layout and actions are saved in a Workspace. All changes made in the ”Preferences” dialog are stored here.