The 4Test Agent is the software process that translates the commands in your
4Test scripts into GUI-specific commands. In other words, it is the Agent that
actually drives and monitors the application you are testing. One Agent can
run locally on the host machine. In a networked environment, any number of
Agents can run on remote machines.
The state you expect your application to be in at the beginning of a testcase.
This is in addition to the conditions required for the base state. See base state.
In QA Organizer, site-specific characteristics that you can define for your
testplan and assign to test descriptions and group descriptions. Each attribute
has a set of values. For example, you define the Developer attribute and
assign it the values of Bob, Carol, Ted, and Alice, the names of the QA
engineers in your department. Attributes are useful for grouping tests, in that
you can run or report on parts of the testplan that have a given attribute value;
for example, all tests that were developed by Bob can be executed as a group.
In SilkTest, an attribute is a characteristic of an application that you verify in
a testcase. Used in the Verify Window dialog.
The known, stable state you expect the application to be in at the start of each
testcase. See DefaultBaseState.
In debugging mode, a list of functions and testcases executing at the time an
error occurred in a script. Listed in reverse order, from the last one executed
back to the first.
Subordinate object in the GUI hierarchy. A child object is either logically
associated with or physically contained by its superior object, the parent. For
example, the File menu, as well as all other menus, are physically contained
by the main window. See parent object.
GUI object type. The class determines which methods can operate on an
object. Each object in the application is an instance of a GUI class.