Quick Test Professional

Quick Test Professional (QTP) is an automated functional Graphical User Interface (GUI)
testing tool that allows the automation of user actions on a web or client based computer
application. It is primarily used for functional regression test automation. QTP uses a
scripting language built on top of VBScript to specify the test procedure, and to
manipulate the objects and controls of the application under test.

TESTING PROCESS

QTP (Quick Test Professional) lets you create tests and business components by
recording operations as you perform them in your application.

Test - A compilation of steps organized into one or more actions, which we can use to
verify that our application performs as expected. A test is composed of actions (3 kinds of
actions are there in QTP Non-reusable action, Reusable action and External action).

1) First step is Planning Before starting to build a test, you should plan it and prepare the
required infrastructure. For example, determine the functionality you want to test, short
tests that check specific functions of the application or complete site.Decide how you
want to organize your object repositories.

2)Second step in QTP is Creating Tests or Components

We can create a test or component by

a) Either recording a session on your application or Web site.

As we navigate through the application or site, QuickTest graphically displays each step
we perform as a row in the Keyword View. The Documentation column of the Keyword
View also displays a description of each step in easy-to-understand sentences. A step is
something that causes or makes a change in your site or application, such as clicking a
link or image, or submitting a data form.
OR b) Build an object repository and use these objects to add steps manually in the
Keyword View or Expert View. We can then modify your test or component with special
testing options and/or with programming statements.

3)Third step is Inserting checkpoints into your test or component. A checkpoint is a

verification point that compares a recent value for a specified property with the expected
value for that property. This enables you to identify whether the Web site or application is
functioning correctly.

4)Fourth step is

Broaden the scope of your test or component by replacing fixed values with parameters.

To check how your application performs the same operations with different data you can
parameterize your test or component.

When you parameterize your test or component, QuickTest substitutes the fixed values in
your test or component with parameters

Each run session that uses a different set of parameterized data is called an iteration.

We can also use output values to extract data from our test or component. An output value
is a value retrieved during the run session and entered into the Data Table or saved as a
variable or a parameter. We can subsequently use this output value as input data in your
test or component.

We can use many functional testing features of QuickTest to improve your test or
component and/or add programming statements to achieve more complex testing goals.

5)Fifth step is running the test

After creating test or component, we run it.

Run test or component to check the site or application.

When we run the test or component, QuickTest connects to your Web site or
application and performs each operation in a test or component, checking any text
strings, objects, or tables you specified. If we parameterized the test with Data Table
parameters, QuickTest repeats the test (or specific actions in your test) for each set of data
values we defined.

Run the test or component to debug it.

We can control the run session to identify and eliminate defects in the test or component.
We can use the

Step Into,

Step Over,

And Step Outcommands to run a test or component step by step. We can also set
breakpoints to pause the test or component at pre-determined points. We can view the
value of variables in the test or component each time it stops at a breakpoint in the Debug
Viewer.

6)Sixth step is analyzing the results

After we run test or component, we can view the results.

? View the results in the Results window.

After running the test or component, we can view the results of the run in the Test Results
window. We can view a summary of the results as well as a detailed report.

? Report defects identified during a run session.

If Quality Center is installed, we can report the defects fond out to a database. We can
instruct QuickTest to automatically report each failed step in the test or component, or we
can report them manually from the Test Results window.

TESTOBJECT MODEL
Test object Model is a set of object types or Classes that QuickTest uses to represents the
objects in our application.

A test object class comprises of a list of properties that can individually (uniquely)
identify objects of that class and a set of appropriate methods that QuickTest can record
for it.

A test object is an object that QuickTest creates in the test to correspond to (represent) the
actual object in the application. QuickTest uses the stored information about the object
during the run session to identify and check the object.

A run-time object is the real (actual) object in the application or Web site on which
methods are performed during the run session.

Properties and methods of objects:

The property set for each test object is created and maintained by QuickTest. The
property set for each run-time object is created and maintained by the object architect
(creator) (Microsoft for Internet Explorer objects, Netscape for Netscape objects).

Similarly, methods of test objects are methods that QuickTest recognizes and records
when they are executed (performed) on an object while we are recording, and that
QuickTest executes when the test or component runs. Methods of Run-time object are the
methods of the object in the application as defined by the object architect (creator). We
can access and execute run-time object methods using the Object property.

Some important points to remember about methods and properties :

• Each test object method we execute (perform) while recording is recorded as a

separate step in the test. When we run the test, QuickTest executes (performs) the
recorded test object method on the run-time object.
 • Properties of test object are captured from object while recording. QuickTest uses
the values of these properties to identify runtime objects in the application during
a run session.
• Property values of objects in the application may change .To make the test object
property values match the property values of the run-time object, we can modify
test object properties manually while designing the test or component or using
SetTOProperty statements during a run session. We can also use regular
expressions to identify property values.
• We can view or modify the test object property values that are stored with the test
or component in the Object Properties or Object Repository dialog box.
• We can view the syntax of the test object methods as well as the run-time methods
of any object on our desktop using the Methods tab of the Object Spy.
• We can retrieve or modify property values of the TEST OBJECT during the run
session by adding GetTOProperty and SetTOProperty statements in the Keyword
View or Expert View. We can retrieve property values of the RUNTIME OBJECT
during the run session by adding GetROProperty statements.

If the available test object methods or properties for an object are not sufficient or they do
not provide the functionality we need, we can access the internal methods and properties
of any run-time object using the Object property. We can also use the attribute object
property to identify Web objects in the application according to user-defined properties.

OBJECT REPOSITORIES

An object as we know is a graphic user element in an application e.g. a button or a list or

an edit box and the special characteristics of an object within the QuickTest are called
object properties. QTP stores the recorded object properties in Object Repository.

Object Repositories are of two types Local and shared.

If objects are stored in a Local Object Repository then these are available to specific
actions but not to all the actions. But if these objects are stored in one or more Shared
Object Repositories then multiple actions or tests can use them.

By default QTP makes and uses Local Object Repository. If we create a new blank test
and do a recording on it, QTP automatically creates a Local Object Repository for that
test or action and stores the information about any object it finds in that corresponding

Object Repository.

In QTP 9 we can associate multiple Shared Object Repositories with an action. If

multiple Shared Object Repositories are associated with an action then also while
recording QTP stores objects in corresponding Local Object Repository on the
condition that those objects are not already stored in any corresponding associated
Shared Object Repositories. This is the default that every time we create a new action
QTP creates a new corresponding Local Object Repository. It is also true that Object
Repositories are associated with actions and no matter how many times we learn or
record on the same object in our application in different actions the object will be stored
as separate test object in each of the Local Object Repository. Local Object Repository
is automatically saved with the test when we save it. The extension of the Local Object
Repository is .mtr, but it is not accessible as a separate file as in case of the Shared
Object Repository.

We can also manipulate some aspects of Local Object Repository using Quick test
Object Repository Automation Object Model. For example we can add, remove,
rename test objects in Local Object Repository. (Quick Test Object Repository
Automation documents the Object Repository automation object model that enables you
to manipulate Quick Test object repositories and their contents from outside of Quick
Test.)

When we open a test that was created using a version of QTP earlier that version 9 we are
asked whether we want to convert it or view it in read only format. In any case if the test
previously used per-action Object Repository, the objects in each per action repository are
moved to the Local Object Repository of each action in the test.

If the test previously used a shared object repository, the same shared object repository is
associated with each of the actions in the test, and the local object repository is empty.

While learning or recording we can specify Shared Object Repository for the selected
action. We can specify and associate one or more Shared Object Repositories with each
action. We can also create new Shared Object Repository and associate it with our
action.

In case of Shared Object Repository, QTP uses existing information and does not add
objects to the Object Repository if we record operations on an object that already exists
either in Shared or Local Object Repository.

As said earlier QTP does not add objects directly to the associated Shared Object
Repository as we record, instead it adds new objects in Local Object Repository (if that
object does not already exist in associated Shared Object Repository).

We can surely export Local objects to Shared Object Repository.

There are different ways in which we can move objects from Local Object Repository
to Shared Object Repository:

1) Exporting the objects to the Shared Object Repository from the Local Object
Repository: In Object Repository window choose the action whose local objects you
want to move. Choose File-> Export Local Objects.Select the location in which you want
to save the file. Click on save.

2) We can update the Shared Object Repository with the Local Object Repository:

f we create a new test it will be created with Local Object Repository, we can associate
any new or old Shared Object Repository with it, and so we can update that Shared
Object Repository with Local Object Repository.

In Object Repository Manager open the Shared Object Repository (clear open in read
only check box).

The test in this case should not be open. In Object Repository Manager go to Tools –>
Update From Local Repository. Select the test who's Local Object Repository you want
to use. Click update all. It will move all the objects to the Shared Object Repository.

3) We can also merge objects from two Object Repositories (called as primary and
secondary in QTP 9) into a new single Object Repository (target Object Repository in
QTP 9). The original source files are not changed. It also enables you to merge objects
from Local Object Repository of one or more action(s) into a Shared Object Repository.
It is recommended to use as a primary Object Repository the file in which you have
invested alot of your effort, like which has more number of objects.
We can compare two Object Repositories using the Object Repository Comparison
Tool. The tool enables you to identify similarities, variations or changes between two
Object Repositories.

We can also copy objects to Local Object Repository from the Shared Object
Repository. We can copy, paste and move objects in Local Object Repository and copy,
paste and move objects within Shared Object Repository and between Shared Object
Repositories.As said earlier we can also copy objects from shared Object Repository to
Local Object Repository to modify them locally

CHECKPOINTS

A checkpoint enables you to identify whether the Web site or application under test is
functioning correctly or not by comparing a current value for a particular property with
the expected value for that property.

After we add a checkpoint, QuickTest adds a checkpoint to the current row in the
Keyword View and adds a Check CheckPoint statement in the Expert View.

By default, the checkpoint name receives the name of the test object on which the
checkpoint is being performed. We can change the name of the checkpoint if needed.

Types of Checkpoints:

• Standard checkpoint.
• Image checkpoints.
• Bitmap Checkpoint.
• Table checkpoints.
• Accessibility Checkpoint.
• Text Checkpoint.
• Page Checkpoint.
 • Database Checkpoint.
• XML checkpoints.

Standard checkpoints allow checking the object property values in the Web site or
application under test. Standard checkpoints evaluate (compare) the expected values of
object properties captured during recording to the object's current values during a run
session. For example we can check that a radio button is activated after it is selected.
Standard checkpoints are supported for all add-in environments.

Standard checkpoints can be used to perform checks on

Images,Tables,Webpage properties, and

Other objects within your application or Web site.

Standard checkpoints can be created for all supported testing environments (as long as
the appropriate add-in(s) are loaded).

Image checkpoints allow you to check the properties of an image in the application or
Web page. For example, you can check that a selected image's source file is correct or
not. An image checkpoint can also be created by inserting a standard checkpoint on an
image object. Image checkpoints are supported for the Web add-in environment

With Bitmap Checkpoint we can check an area of a Web page or application as a bitmap.
While creating a test, we have to specify the area to check by selecting an object. An
entire object or any area within an object can be checked. Bitmap checkpoints are
supported for all add-in environments

By adding table checkpoints to the test, we can check the content of tables displayed in
the application. For example, we can check that a specified value is displayed in a certain
cell. Certain environments also support checking the properties of the table object. For
example, a check that a table has the expected number of rows and columns. A table
checkpoint can also be created by inserting a standard checkpoint on a table object.

Accessibility Checkpoint recognizes areas of your Web site that may not conform to the
World Wide Web Consortium (W3C) Web Content Accessibility Guidelines. For
example, check if the images on a Web page include ALT properties, required by the
W3C Web Content Accessibility Guidelines.

Accessibility checkpoints are supported for the Web add-in environment

QuickTest can check that a text string is displayed in the appropriate place in an
application or on a Web page with Text Checkpoint. Text checkpoints are supported for
the Web add-in environment, plus some Web-based add-in environments

Page Checkpoint checks the features of a Web page. For example, you can check how
long a Web page takes to load or whether a Web page contains broken links. A page
checkpoint can also be created by inserting a standard checkpoint on page object. Page
checkpoints are supported for the Web add-in environment

The contents of a database accessed by your application can be checked by Database

Checkpoint. Database checkpoints are supported for all add-in environments

By adding XML checkpoints to your test, you can check the contents of individual XML
data files or documents that are part of your Web application. The XML Checkpoint
option is supported for all add-in environments.

QTP RECORDING

The default mode of recording is the Normal recording mode. There are other

recording modes also like Analog Recording or Low Level Recording. Normal mode is
the default and takes full advantage of the QuickTest test object model, as it recognizes
the objects in the application regardless of their location on the screen.

Analog Recording : Exact mouse and keyboard operations are recorded in relation to
either the screen or the application window. In this QTP also records and tracks every
movement of the mouse for example, recording a signature produced by dragging the
mouse. Analog Recording steps are not editable from within QuickTest.

Low Level Recording : At any time, if an environment or on an object not recognized by

QuickTest, use Low Level Recording. It records at object level and records all run-time
objects as Window or WinObject test objects. QuickTest records all parent level objects
as Window test objects and all other objects as WinObject test objects.

Each step recorded in Low Level Recording mode is shown in the Keyword View and
Expert View. All the three modes of recording can be used in a single test e.g. we can
switch to either Analog Recording or Low Level Recording in the middle of a
recording session for specific steps and then return to normal recording mode.

Analog Recording and Low Level Recording require more disk space than normal
recording mode.

Use Analog Recording when :

The actual movement of the mouse is what you want to record.

Recording in Analog mode can be relative to the screen or relative to a specific window

In Analog Recording a separate file is saved and stored with the action.

In Analog Recording mode, QuickTest adds to your test a RunAnalog statement that
calls the recorded analog file.

Use Low Level Recording when :

Environments or objects not supported by QuickTest.

Exact location of the operation on your application screen is necessary. in normal mode
QuickTest performs the step on an object even if it has moved to a new location on the
screen.

If the location of the object is important to your test, switch to Low Level Recording.

Parameterizing Tests in QTP (QuickTest Professional)

By replacing fixed values with parameters QuickTest enables you to enlarge the scope
of a basic test. It is known as parameterization, greatly increases the power and
flexibility of a test. A parameter is a variable that is assigned a value from an external
data source or generator. Values in steps and checkpoints and also the values of action
parameters can be parameterize.

Parameters let us check how the application performs the same operations with multiple
sets of data.

There are four types of parameters:

Test/action parameters: Test parameters make possible for us to use values passed
from the test. Action parameters enable us to pass values from other actions in your test.
To use a value within a specific action, the value must be passed down through the action
hierarchy of the test to the required action. We can then use that parameter value to
parameterize a step in the test. For example, suppose that we want to parameterize a step
in Action3 using a value that is passed into the test from the external application that runs
(calls) the test. We can pass the value from the test level to Action1 (atop-level action) to
Action3 (a nested action of Action1), and then parameterize the required step using this
action input parameter value (that was passed through from the external application).
Alternatively, we can pass an output action parameter value from an action step to a later
sibling action at the same hierarchical level. For example, suppose that Action2, Action3,
and Action4 are sibling actions at the same hierarchical level, and that these are all nested
actions of Action1. We can parameterize a call to Action4 based on an output value
retrieved from Action2 or Action3. We can then use these parameters in the action step.

Data Table parameters allow us to create a data-driven test (or action) that runs several
times using the data that we supply. In each repetition, or iteration, QuickTest uses a
different value from the Data Table.

Environment variable parameters allow us to use variable values from other sources
during the run session. These may be values that we supply, or values that QuickTest
generates for us based on conditions and options we choose.

Random number parameters enable us to insert random numbers as values in your test.

Values in steps and checkpoints can be parameterized while recording or editing the test.

The values of object properties can be parameterized for a selected step.

The values of the operation (method or function arguments) defined for the step can also
be parameterized.

When the value of an object property for a local object is parameterized, we are
amending the test object description in the local object repository. Therefore, all
occurrences of the specified object within the action are parameterized.
Parameterizing the value of a checkpoint property enables us to check how an application
or Web site performs the same operation based on different data.

QTP (QuickTest Professional) keyword view

In QTP (QuickTest Professional) we first of all record a test, then run a test and then
analyze the results, but before running the test we can also enhance it with checkpoints
and parameters.

First of all let's talk a little about keyword view in QTP and then we will talk about
recording in QTP and then we will move on to other things.

After recording all the operations, QuickTest displays them as steps in the Keyword
View, and generates them in a script (in an Expert View).

In the keyword view there are 4 visible columns –

Item- The item on which we want to perform the step and it can be a test object, utility
object, function call, or statement. This column shows a hierarchical icon-based tree. The
highest level of the tree is actions, and all steps are contained within the relevant branch
of the tree.

Operation- The operation (methods or functions) to be performed on the item selected in

the Item column, for example, Click or Select.

Value- The argument values for the selected operation, for example, the mouse button to
use when clicking the image.

Documentation- It is a Read-only auto-documentation of what the step does in an easy-

to-understand sentence, for example, Click the "findFlights" image.

Assignment- The assignment of a value to or from a variable for example, Store in cCols
would store the return value of the current step in a variable called cCols so you can use
the value later in the test. This column is not visible by default.
Comment- Any textual information you want to add regarding the step. This column is
also not visible by default.
Actions in QTP 9 (QuickTest Professional)

Actions break up the test into logical sections/units such as specific activities that we
perform in our application.

When we create a new test, it contains a call to one action. By breaking up the tests into
calls to multiple actions, we can design more modular and well organized and
professional tests. An action has its own test script, containing all of the steps recorded in
that action, and all objects in its local object repository. An action is stored with the test in
which you created it.

If you create a test in which you log into the system (email), check inbox, and then log
out of the system (email), your test might be structured as shown—one test calling three
separate actions:

Test 1 Actions stored with Test 1

Call to action 1 ---> Action 1(Logging In)
Call to action 2 ---> Action 2(Checking Inbox Mails)
Action 3(Logging Out)
Call to action 3 --->

Actions make it possible to parameterize and iterate over specific elements of a test. They
also make it easier to re-record steps in one action when part of your application changes.
For every action called in the test, QuickTest creates a corresponding action sheet in the
Data Table so that we can enter Data Table parameters that are specific to that action
only.

Three types of actions are: Non-reusable action This non reusable action can be
called only once and that too in the test with which it is stored.

Reusable action Reusable actions are like functions in any programming language. If
there is a process that needs to be included in several tests, we can record, modify, and
enhance the steps of the process and save them in a reusable action. Then we can call the
action from other tests, rather than recording, modifying, and enhancing the same steps
each time. It can be called several times by the test with which it is stored (the local test),
as well as by other tests.

Deleting a reusable action that is called by other tests will cause those tests to fail.

External action is a reusable action stored with another test. External actions are read-
only in the calling test, but we can choose to use a local, editable copy of the Data Table
information for the external action. When a call to an external action is inserted, the
action is inserted in read-only format

We can create an additional call to any reusable or external action in the test by pressing
CTRL while we drag and drop the action to another location at a parallel (sibling) level
within the test.

By default, new actions are non-reusable. Each action created in a test can be marked as
reusable or non-reusable.

When we run a test with multiple actions, the test results are divided by actions within
each test iteration so that we can see the outcome of each action, and can view the
detailed results for each action individually.

If you expect other users to open your tests and all actions in your tests are stored in the
same drive, you should use relative paths for your reusable actions so that other users will
be able to open your tests even if they have mapped their network drives differently.

VBScript in QTP

Scripting language for Quick Test Professional (QTP) is VBScript.

VBScript (short for Visual Basic Scripting Edition) is a lively Scripting language
interpreted via Microsoft's Windows Script Host.

VBScript has many powerful functions and provides excellent support for variables, data
types, and error handling.

Two script engines can interpret VBScript- VBScript.dll, which is invoked by asp.dll is
used in web environment and Wscript.exe & Cscript.exe in Windows GUI environment
using Windows script Host (WSH, We typically use VBScript within WSH to automate
systems administration tasks. WSH is the system module that transforms a VBScript file
into a Windows executable file). Wscript.exe is used to display output and receive input
in Windows GUI format such as dialog and input boxes. Cscript.exe is used in a
command-line environment. When VBScript source code is contained in stand-alone
files, they have the file extension .vbs