Glossary - regression testing
by using an include statement. Portion of a testplan that lives in a separate file
but can be expanded inline within its master plan. A subplan may contain the
levels of group description and test description not covered in the master
plan. A subplan can inherit information from its master plan. You add a
subplan by inserting an include statement in the master plan. A subplan file
has a .pln extension, as in subplan-name.pln. See also master plan.
each script individually, you run the suite, which executes in turn each of
your scripts and all the testcases it contains.
can be defined at a level in the testplan where it can be shared by a group of
tests. Its values are actually assigned at either the group or test description
level, depending on whether the values are shared by many tests or are unique
to a single test. Similar to a 4Test identifier, except that its name begins with a
$ character.
SilkTest locates and identifies objects in the application.
creating a new testplan. Based on the window declarations in the frame file.
executed. Test descriptions by default are displayed in blue. See also group
description.
declarations, user-defined classes, utility functions, constants, and variables,
as well as other include files.
Specifically, a 4Test function that begins with the testcase keyword and
contains a sequence of 4Test statements. It drives an application to the state to
be tested, verifies that the application works as expected, and returns the
application to its base state.
defined in a script file. Used in an assignment statement to link a test
description in a testplan with a 4Test testcase defined in a script file.
testplan is displayed in an easy-to-read outline format, which lists the test
requirements in high-level prose descriptions. The structure can be flat or
many levels deep. Indentation indicates the level of detail. A testplan also