o

Test Process Workflow:

Analyzing the application (Add_ins, Action splitting
etc.)
Prepare testing infrastructure (Repository,
Configure, Action repository)
Adding steps to Actions (Drag and drop, Write
scripts)
Enhance your test (Checkpoints, Parameterization,
Output values User defined function etc.)
Running and Debugging your test (Step into, Step
over, Step out, Breakpoints, Maintenance run etc.)
Analyzing run results and defect reporting

The Debug Viewer pane assists you in debugging your tests or function libraries,
and contains the following tabs:
Tab Description
Watch: Displays the current value and type of any variable or VBScript expression
that you added to the Watch tab. You can also set or modify the values of the
variables and properties that are displayed.
Variables (Local Variable in UFT): Displays the current value and type of all
variables that were recognized up to the last step performed during the run
session that you are debugging. You can also set or modify the values of the
variables that are displayed.
Command (Console in UFT): Enables you to run lines of script to set or modify
the current value of a variable or VBScript object in your test or function library
(e.g: if a=hhhh then b=iii endif)

o
o

Breakpoint shortcut F9/ Step Into F11/ Step Over F10/ Step Out Shift+F11
Step Into: Runs only the current line of the script. If the current line calls a
method, the method is displayed in the view but is not performed (Takes to
the code and each line is executed sequentially)
Step over: Runs only the current line of the script. When the current line
calls a method, the method is performed in its entirety but is not displayed
in the view (Code is not displayed however code is run and output is
displayed i.e. it will execute the entire function instead of going line by
line)
Step Out: Runs to the end of the method when pauses the run session (It
is available only after running Step Into) (Takes to the code however only
output is displayed i.e. it executes all other functions at a time)
If a file is called using an ExecuteFile statement, you cannot debug the
file or any of the functions contained in the file

Process Guidance Panes at a Glance (not in uft)

o

Process guidance is a tool that provides procedures and descriptions on how to

best perform specific processes, such as creating a test in QuickTest. You use
process guidance to learn about new processes and to learn the preferred
methodology for performing processes with which you are already familiar. Your
organization may also provide you with process guidance that is accessible from
these panes. Process guidance is displayed in two panes:
Process Guidance Activities pane (shown on the left). Lists the activities that
are part of the selected process, such as adding steps to a test.

 Process Guidance Description pane (shown on the right). Describes the tasks
that you need to perform for a selected activity
o
o

o
o

Action Properties: Enables to specify options, parameters and associated

OR
Action Call properties: Enable to specify number of rum iterations,
define values of input parameter and storage location of output
parameter.

Action Properties: Option to make action as Reusable, Define input and

output parameters, Associate OR
Action call properties: Run options like how many iteration (data table
parameterization), Assign parameter values, Select output value storage
location
A test object is an object that QuickTest creates in the test to represent the
actual object in your application. QuickTest stores information on the object that
will help it identify and check the object during the run session.
A run-time object is the actual object in your application on which methods are
performed during the run session
When you run a test, QuickTest identifies each object in your application by its
test object class and its description

Test Object
Are QTP defined class
Stored in OR
For a specific environment can be viewed in
object identification config
Properties are created by QTP
Get To Property

Run Time Object

Are actual objects in AUT
Accessed through Object spy

methods are methods that QuickTest

recognizes and records when they are
performed on an object while you are
recording a test, and that QuickTest
performs when your test runs.

methods are the methods of the object in

your application as defined by the object
creator

o
o
o
o

Properties are created by object creator

Get RO Property

You cannot move an object to any of its descendants.

You cannot copy or move an object to be a child of a bottom-level object (an
object that cannot contain a child object) in the object hierarchy
You can choose to only export the local objects to a shared object repository, or to
export and replace the local objects. The Export and Replace Local Objects option
exports the local objects to a shared object repository, associates the new shared
object repository with your action, and deletes the objects in the local object
repository
When you export local objects to a shared object repository, the parameters of
any parameterized objects are converted to repository parameters using the
same name as the source parameter

Message Statements
You can generate messages in your test that are displayed in the Run Results
Viewer. You can also choose to display messages on screen while running your
test
You can send the following types of messages to the run results:
Test-specific messages. You can add notes run results to provide additional
information about the test run. For example, you can specify the application

version tested, the operating system used, languages, and so on. In the Run
Results Viewer, this information is displayed in the Executive Summary page.
You add a note by inserting a Reporter.ReportNote step in your test
Step-specific messages. You can define a message that QuickTest sends to your
run results. For example, suppose you want to check that a password edit box
exists in the Mercury Tours site. If the edit box exists, then a password is entered.
Otherwise, QuickTest sends a message to the run results indicating that the object
is absent. You send messages to the run results using the Insert Report dialog box.
When you add a report step, a Reporter.ReportEvent step is inserted.

o
o

Action Types:
Reusable action: An action that can be called multiple times by the test with

which it is stored (the local test), as well as by other tests. By default, new actions
are reusable. You can mark each action you create in a test as reusable or nonreusable. Only reusable actions can be called multiple times from the current test
or from another test. Inserting calls to reusable actions makes it easier to
maintain your tests, because when an object or procedure in your application
changes, it needs to be updated only one time, in the original action.
Non-reusable action: An action that can be called only in the test with which
it is stored, and can be called only once. You can store a copy of a non-reusable
action with your test and then insert a call to the copy, but you cannot directly
insert a call to a non-reusable action saved with another test.
External action: A reusable action stored with another test. External actions
are read-only in the calling test, but you can choose to use a local, editable copy
of the data table information for the external action