8/11/2019 QTP_Basic

1/42

22 October 2010

Functional Test Automation With

HP/Mercury

QuickTest Professional

8/11/2019 QTP_Basic

2/42

22 October 2010 2

Multi-Document Chapter Summary

QuickTest Professional Training Material is divided into two Documents (PPTs):

1.Functional Test Automation With HP/Mercury QuickTest Professional

This document introduces QuickTest and describes the basic features that are used ineveryday testing.

2.QTP Advanced Features

This document describes advanced features like descriptive programming that you can

use when testing applications. It also describes how to work with other Mercury

products.

8/11/2019 QTP_Basic

3/42

22 October 2010

3

Using This Document

This document describes how to use QuickTest to test your applications. It provides basic

guidelines to help you create, debug, and run tests, and report defects detected during

the testing process. This document contains the following parts:

PART I: INTRODUCTION TO TEST AUTOMATION

PART II: INTRODUCING QUICKTEST PROFESSIONAL

PART III: CREATING TESTS

PART IV: DEBUGGING TESTS AND FUNCTION LIBRARIES

PART V: RUNNING TESTS & ANALYZING TEST RESULTS

8/11/2019 QTP_Basic

4/42

22 October 2010

4

PART I: INTRODUCTION TO TEST AUTOMATION

8/11/2019 QTP_Basic

5/42

22 October 2010

5

Types of Testing

ManualUsage of steps defined within test cases to manually test the application to

ensure that it functions properly

Automated

Automation of the manual testing process to all unattended execution andensure repeatability

Benefits of Automated Testing

Speed Automated tests are fast and can execute at a speed faster than a person can

click

Reliable

The tests can perform the exact same steps every time without concern abouthuman error

Repeatable

You run the same test against multiple builds/versions of an application

Reusable Can be reused as a sub-part of different tests

8/11/2019 QTP_Basic

6/42

22 October 2010

6

What Should Be Automated

Good candidates

Tests executed for each build

Business critical tests Tests that are difficult/tedious to perform manually

Bad candidates

Tests without predictable results

Test that require variable input/responses from the tester

Tests that perform operations in multiple environments

8/11/2019 QTP_Basic

7/42

22 October 2010

7

PART II: INTRODUCING QUICKTEST PROFESSIONAL

8/11/2019 QTP_Basic

8/42

22 October 2010

8

What is QuickTest Professional (QTP)What is QuickTest Professional (QTP)

It is an automated testing tool provided by HP/Mercury Interactive

An advanced solution for functional and regression test automation.

Enables you to test standard Windows applications, Web objects, ActiveX controls, andVisual Basic applications. You can also acquire additional QuickTest add-ins for a numberof special environments (such as Java, Oracle, SAP Solutions, .NET Windows and WebForms, Siebel, PeopleSoft, Web services, and terminal emulator applications).

Uses industry standard VBScript to create and run tests

High programmability using desktop environments

QTP integrates with other Mercury testing solutions including:

Quality Center WinRunner

LoadRunner

Utilizes an add-in architecture for compactness and extensibility

8/11/2019 QTP_Basic

9/42

22 October 2010

9

Plan Test

Run Test

Verify & Enhance

Debug Test

Preparation for recording

Record User Actions to generate the basic test

Enhance the Automated test for Play Back and Testing

Report the defect using Excel templates / defect tracking tool.

QTP Script Development Workflow

Learn & RecordTest

Analyze TestResults

ReportingDefects

You debug a test to ensure that it operates smoothly and

without interruption.

You run a test to check the behavior of your application or Website.

You examine the test results to pinpoint defects in your

application.

For more information on QTP introduction see part I, Introducing QuickTest Professional of

Mercury QuickTest Professional Basic Features Users Guide.

8/11/2019 QTP_Basic

10/42

22 October 2010

10

PART III: CREATING TESTS

8/11/2019 QTP_Basic

11/42

22 October 2010

11

Launching QuickTest Tool

To start QuickTest, choose Programs > QuickTest Professional > QuickTestProfessional in the Start menu, or double-click the QuickTest Professional shortcut on

your desktop.

The first time you start QuickTest, theAdd-in Manager dialog box opens as below.

8/11/2019 QTP_Basic

12/42

22 October 2010

12

Starting QuickTest

Click OK on Add-in Manager dialog box. The QuickTest Professional window opens. Youcan choose to open the QuickTest tutorial, start recording a new test, open an existing

test, or open a blank new test.

For more information on Starting QuickTest see part I, QuickTest at a Glance of

Mercury QuickTest Professional Basic Features Users Guide.

8/11/2019 QTP_Basic

13/42

22 October 2010

13

Keyword View

The Keyword View enables you to create and view the steps of your test in a keyword-driven, modular, table format. The Keyword View is comprised of a table-like view, in

which each step is a separate row in the table, and each column represents different parts

of the steps. You can modify the columns displayed to suit your requirements.

8/11/2019 QTP_Basic

14/42

22 October 2010

14

Expert View

In the Expert View, QuickTest displays each operation performed on your application in the

form of a script, comprised of VBScript statements. The Expert View is a script editor with

many script editing capabilities. For each object and method in an Expert View statement,

a corresponding row exists in the Keyword View.

8/11/2019 QTP_Basic

15/42

22 October 2010

15

QTP Recording Modes

Normal Recording - The actions performed on the standard objects are recorded usingNormal Recording mode.

Analog Recording - Enables you to record the exact mouse and keyboard operations

you perform in relation to either the screen or the application window. In this recordingmode, QuickTest records and tracks every movement of the mouse as you drag themouse around a screen or window.

Low-Level Recording - Enables you to record on any object in your application,

whether or not QuickTest recognizes the specific object or the specific operation. Thismode records at the object level and records all run-time objects as Window orWinObject test objects. Use this, if you want to record / capture the exact co-ordinatesof the object and the mouse movements.

Note: Steps recorded using low-level mode may not run correctly on all objects.

For more information on QTP Recording Modes see part II, Recording a Test ofMercury QuickTest Professional Basic Features Users Guide.

8/11/2019 QTP_Basic

16/42

22 October 2010

16

Learns the objects parent window and the object properties.

Recognizes the object type (class).

Assigns a Logical Name to the learned object.

How QTP identifies the Objects

Application UnderTest (AUT)

QuickTest Pro(QTP)

ObjectRepository (OR)

QTP reads the logicalname from the AUT andrefer to the ObjectRepository for that

object.

QTP reads the logicalname from the AUT andrefer to the ObjectRepository for thatobject.

Object Repositorycontains all the Objectslogical names and thephysical descriptions.

Object Repositorycontains all the Objectslogical names and thephysical descriptions.

QTP identifies the AUTobjects based on thephysical descriptions ofthe objects

QTP identifies the AUTobjects based on thephysical descriptions ofthe objects

For more information on Object Identification in QTP see chapter 6 of part II, Workingwith Test Objects of Mercury QuickTest Professional Basic Features Users Guide.

8/11/2019 QTP_Basic

17/42

22 October 2010

17

Object Spy

Using the Object Spy, you can view the properties of any object in an open application.You use the Object Spy pointer to point to an object. The Object Spy displays the

selected objects hierarchy tree and its properties and values in the Properties tab of the

Object Spy dialog box.

To view object properties:

1.Open your browser or application to the page containing the object on which you want

to spy.

2.Choose Tools > Object Spy or click the Object Spy toolbar button to open the Object

Spy dialog box and display the Properties tab. Alternatively, click the Object Spy button

from the Object Repository dialog box.

3.In the Object Spy dialog box, click the pointing hand. Both QuickTest and the Object

Spy are minimized so that you can point to and click on any object in the open

application.

8/11/2019 QTP_Basic

18/42

22 October 2010

18

Object Repository

The Object Repository window displays a tree of all objects in the selected action(including all local objects and all objects in any shared object repositories associatedwith the selected action).

For each test object you select in the tree, the Object Repository window displaysinformation about the test object, its type, the repository in which it is stored, and its testobject details. Local objects are editable (black); shared objects are in read-only format(gray).

While the Object Repository window is open, you can continue using QuickTest, andyou can continue modifying test objects and object repositories. You can also resize theObject Repository window if needed.

The Object Repository window reflects any changes you make to an associated object

repository in real-time. For example, if you add objects to the local object repository, orif you associate an additional object repository with the current action, the ObjectRepository window immediately displays the updated content.

For more information on Object Repository see chapter 6 of part II, Working with

Test Objects of Mercury QuickTest Professional Basic Features Users Guide.

8/11/2019 QTP_Basic

19/42

22 October 2010

19

Checkpoints

QuickTest enables you to add checks to your test. A checkpoint is a verification point

that compares a current value for a specified property with the expected value for that

property. This enables you to identify whether your Web site or application is functioning

correctly.

When you 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. You can choose to specify a different name for the checkpoint or

accept the default name.

When you run the test, QuickTest compares the expected results of the checkpoint to

the current results. If the results do not match, the checkpoint fails. You can view the

results of the checkpoint in the Test Results window.

8/11/2019 QTP_Basic

20/42

22 October 2010

20

Types of Checkpoints

You can insert the following checkpoint types to check various objects in a Web site or

application.

Standard Checkpoint checks the property value of an object in your application or Web

page. The standard checkpoint checks a variety of objects such as buttons, radio

buttons, combo boxes, lists, and so forth. For example, you can check that a radio

button is activated after it is selected or you can check the value of an edit box.

Image Checkpoint checks the value of an image in your application or Web page. Forexample, you can check that a selected images source file is correct.

Bitmap Checkpoint checks an area of your Web page or application as a bitmap. For

example, suppose you have a Web site that can display a map of a city the user

specifies. The map has control keys for zooming. You can record the new map that is

displayed after one click on the control key that zooms in the map. Using the bitmap

checkpoint, you can check that the map zooms in correctly.

8/11/2019 QTP_Basic

21/42

22 October 2010

21

Types of Checkpoints (Contd.,)

Table Checkpoint checks information within a table. For example, suppose your

application or Web site contains a table listing all available flights from New York to San

Francisco. You can add a table checkpoint to check that the time of the first flight in the

table is correct.

Text Checkpoint checks that a text string is displayed in the appropriate place on a Web

page or application. For example, suppose a Web page displays the sentence Flight

departing from New York to San Francisco. You can create a text checkpoint that

checks that the words New York are displayed between Flight departing from and to

San Francisco.

Accessibility Checkpoint identifies areas of your Web site that may not conform to the

World Wide Web Consortium (W3C) Web Content Accessibility Guidelines. For

example, guideline 1.1 of the W3C Web Content Accessibility Guidelines requires youto provide a text equivalent for every non-text element. You can add an Alt property

check to check whether objects that require the Alt property under this guideline, do in

fact have this tag.

8/11/2019 QTP_Basic

22/42

22 October 2010

22

Types of Checkpoints (Contd.,)

Page Checkpoint checks the characteristics 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.

Database Checkpoint checks the contents of a database accessed by your application.

For example, you can use a database checkpoint to check the contents of a database

containing flight information for your Web site.

XML Checkpoint checks the data content of XML documents in XML files or XMLdocuments in Web pages and frames.

For more information on Check Points see chapter 7 of part II, Understanding

Checkpoints of Mercury QuickTest Professional Basic Features Users Guide.

8/11/2019 QTP_Basic

23/42

22 October 2010

23

Regular Expressions

Regular expressions enable QuickTest to identify objects and text strings with varyingvalues. You can use regular expressions when:

1.defining the property values of an object in dialog boxes or in programmaticdescriptions

2.parameterizing a step

3.creating checkpoints with varying values

For example, you can use a regular expression if you want to create a text checkpoint on

a date text string, but the displayed date changes according to the current date. If youdefine the date as a regular expression, the checkpoint checks that the captured textstring matches the expected date format, rather than checking the exact date value.

A regular expression is a string that specifies a complex search phrase. By using

special characters, such as a period (.), asterisk (*), caret (^), and brackets ([ ]), you candefine the conditions of a search.

For more information on Regular Expressions see chapter 14 of part II, ConfiguringValues of Mercury QuickTest Professional Basic Features Users Guide.

8/11/2019 QTP_Basic

24/42

22 October 2010

24

Parameterizing

Values

QuickTest enables you to expand the scope of a basic test by replacing fixed valueswith parameters. This process, known as parameterization, greatly increases the power

and flexibility of your test.

You can parameterize values in steps and checkpoints in your test. You can also

parameterize the values of action parameters.

If you wish to parameterize the same value in several steps in your test, you may want

to consider using the Data Driver rather than adding parameters manually.

There are four types of parameters:

Test/action parameters

Data Table parameters

Environment variable parameters Random number parameters

For more information on Parameterizing Values see chapter 15 of part II,

Parameterizing Values of Mercury QuickTest Professional Basic Features Users

Guide.

8/11/2019 QTP_Basic

25/42

8/11/2019 QTP_Basic

26/42

22 October 2010

26

Creating Output Values

When you add an output value step to your test, you first select the category of values

to output, for example, property values, text values, or XML element values. You can

then determine which values to output. You also determine the storage location for each

value.

You can create the following categories of output values:

Standard output values

Text output values Table output values

Database output values

XML output values

For more information on Output Values see chapter 16 of part II, Outputt ing Values

of Mercury QuickTest Professional Basic Features Users Guide.

8/11/2019 QTP_Basic

27/42

22 October 2010

27

Virtual Objects

You can teach QuickTest to recognize any area of your application as an object bydefining it as a virtual object. Virtual objects enable you to record and run tests onobjects that are not normally recognized by QuickTest.

Your application may contain objects that behave like standard objects but are not

recognized by QuickTest. You can define these objects as virtual objects and map themto standard classes, such as a button or a check box.

QuickTest emulates the users action on the virtual object during the run session. In thetest results, the virtual object is displayed as though it is a standard class object.

For example, suppose you want to record a test on a Web page containing a bitmapthat the user clicks. The bitmap contains several different hyperlink areas, and eacharea opens a different destination page. When you record a test, the Web site matchesthe coordinates of the click on the bitmap and opens the destination page.

8/11/2019 QTP_Basic

28/42

22 October 2010

28

Defining and Using Recovery Scenarios

You can instruct QuickTest to recover from unexpected events and errors that occur in

your testing environment during a run session.

Unexpected events, errors, and application crashes during a run session can disrupt

your run session and distort results. This is a problem particularly when running testsunattendedthe test is suspended until you perform the operation needed to recover.

The Recovery Scenario Manager provides a wizard that guides you through the process

of defining a recovery scenarioa definition of an unexpected event and theoperation(s) necessary to recover the run session.

For example, you can instruct QuickTest to detect a Printer out of paper message and

recover the run session by clicking the OK button to close the message and continue

the test.

8/11/2019 QTP_Basic

29/42

22 October 2010

29

Working with Actions

You can divide your test into actions to streamline the process of testing yourapplication or Web site. This chapter covers the basic use of actions in your test.

Actions help divide your test into logical units, such as the main sections of a Web site,or specific activities that you perform in your application.

A test comprises calls to actions. When you create a new test, it contains a call to asingle action. By creating tests that call multiple actions, you can design tests that aremore modular and efficient.

An action consists of its own test script, including all of the steps recorded in that action,and any objects in its local object repository.

Each action is stored together with the test in which you created it. You can insert a call

to an action that is stored with the test and, depending on the properties of the action,you may also be able to call an action stored with another test.

For more information on Actions see chapter 17 of part II, Working with Actions ofMercury QuickTest Professional Basic Features Users Guide.

8/11/2019 QTP_Basic

30/42

22 October 2010

30

Working with Data Tables

The data your test uses is stored in the design-time Data Table, which is displayed in

the Data Table pane at the bottom of the screen while you insert and edit steps.

The Data Table has the characteristics of a Microsoft Excel spreadsheet, meaning that

you can store and use data in its cells and you can also execute mathematical formulaswithin the cells. You can use the DataTable, DTSheet and DTParameter utility objects

to manipulate the data in any cell in the Data Table.

You can insert Data Table parameters and output values into your test. Using DataTable parameters and/or output values in a test enables you to create a data-driven test

or action that runs several times using the data you supply.

In each repetition, or iteration, QuickTest uses a different value from the Data Table.

During the run session, QuickTest creates a run-time Data Tablea live version of the

Data Table associated with your test. During the run session, QuickTest displays the

run-time data in the Data Table pane so that you can see any changes to the Data

Table as they occur.

8/11/2019 QTP_Basic

31/42

22 October 2010

31

Using Global and Action Data Sheets

When you output a value to the Data Table or add a Data Table parameter to your test,

you can specify whether to store the data in the Global data sheet or in the action data

sheet.

Choosing Global sheet enables you to create a new column or select an existingcolumn in the Global sheet in the Data Table. When you run your test, QuickTest insertsor outputs a value from or to the current row of the Global data sheet during each globaliteration. You can use the columns in the Global data sheet for Data Table outputvalues or Data Table parameters in any action. This enables you to pass informationbetween actions.

Each action also has its own sheet in the Data Table so that you can insert data thatapplies only to that action. Choosing Current action sheet (local) enables you to createa new column or select an existing column in the corresponding action sheet in the DataTable. When you run your test, QuickTest inserts or outputs a value from or to thecurrent row of the current action (local) data sheet during each action iteration.

When there are parameters or output value steps in the current actions sheet, you canset QuickTest to run one or more iterations on that action before continuing with thecurrent global iteration of the test. When you set your action call properties to runiterations on all rows, QuickTest inserts the next value from or to the correspondingaction parameter or output value during each action iteration, while the values of the

global parameters stay constant.

8/11/2019 QTP_Basic

32/42

22 October 2010

32

Saving the Data Table

The Data Table contains the values that QuickTest substitutes for Data Table

parameters when you run a test, as well as any other values or formulas you enter.

Whenever you save your test, QuickTest automatically saves its Data Table as an .xls

file.

When working with tests, the Data Table is saved with your test by default.

You can save the Data Table in another location and instruct the test to use this Data

Table when running a test. You specify a name and location for the Data Table in theResources tab of the Test Settings dialog box.

For more information on Data Tables see chapter 19 of part II, Working with Data

Tables of Mercury QuickTest Professional Basic Features Users Guide.

8/11/2019 QTP_Basic

33/42

22 October 2010

33

Synchronization

When you run a test, your application may not always respond with the same speed. Forexample, it might take a few seconds:

for a progress bar to reach 100%

for a status message to appear for a button to become enabled

for a window or pop-up message to open

You can handle these anticipated timing problems by synchronizing your test to ensurethat QuickTest waits until your application is ready before performing a certain step.

There are several options that you can use to synchronize your test:

1.You can insert a synchronization point, which instructs QuickTest to pause the test until

an object property achieves the value you specify. When you insert a synchronization

point into your test, QuickTest generates a WaitProperty statement in the Expert View.

2.You can insert Exist or Wait statements that instruct QuickTest to wait until an object

exists or to wait a specified amount of time before continuing the test.

8/11/2019 QTP_Basic

34/42

22 October 2010

34

Synchronization (Contd.,)

3. You can modify the default amount of time that QuickTest waits for a Web page toload.

4. When working with tests, you can increase the default timeout settings for a test in

order to instruct QuickTest to allow more time for objects to appear.

How to synchronize the Test?

We can synchronize the test by

1.Inserting a synchronization point

Insert Step Synchronization point

Window(Flights ).WinButton( Update order ).WaitProperty enabled ,1,1000

2. Adding Exist and Wait statements

status=Window( Flights ).Dialog( Flights Table ).Exist

Wait(10)

8/11/2019 QTP_Basic

35/42

22 October 2010

35

PART IV: DEBUGGING TESTS AND FUNCTION LIBRARIES

8/11/2019 QTP_Basic

36/42

22 October 2010

36

Debugging Tests and Function Libraries

By controlling and debugging your run sessions, you can identify and handle defects in

your tests, function libraries, and registered user functions. After you create a test or

function library (including registered user functions), you should check that they run

smoothly, without errors in syntax or logic. To debug a function library, you must first

associate it with a test and then debug it from that test.

To detect and isolate defects in a test or function library, you can control the run session

using the Pause command as well as various step commands that enable you to step

into, over, and out of a specific step. You can use the Start from Step command to

begin your debug session at a specific point in your test. You can also use the Run toStep command to pause the run at a specific point in your test. You can set

breakpoints, and then enable and disable them as you debug different parts of your test

or function library.

When the test or function library run stops at a breakpoint, you can use the Debug

Viewer to check and modify the values of VBScript objects and variables. Also, if

QuickTest displays a run error message during a run session, you can click the Debug

button on the error message to suspend the run and debug the test or function library.

8/11/2019 QTP_Basic

37/42

22 October 2010

37

Using Breakpoints

You can use breakpoints to instruct QuickTest to pause a run session at a predetermined

place in a test or function library. QuickTest pauses the run when it reaches the

breakpoint, before executing the step. You can then examine the effects of the run up to

the breakpoint, make any necessary changes, and continue running the test or function

library from the breakpoint.You can use breakpoints to:

Suspend a run session and inspect the state of your site or application

mark a point

from which to begin stepping through a test or function library using the step commands

You can set breakpoints, and you can temporarily enable and disable them.

After you finish using them, you can remove them from your test or function library.

To set a breakpoint, Perform one of the following:

Click in the left margin of a step in the test or function library where you want the run to

stop

Click a step and then:

1.Click the Insert/Remove Breakpoint button

2.Choose Debug > Insert/Remove Breakpoint

3.Press F9

8/11/2019 QTP_Basic

38/42

22 October 2010

38

PART V: RUNNING TESTS & ANALYZING TEST RESULTS

8/11/2019 QTP_Basic

39/42

22 October 2010

39

Running Tests

After you create a test, you can run it to check the behavior of your application. When

you run a test, QuickTest performs the steps it contains.

If you have defined test parameters, QuickTest prompts you to enter values for them.

When the run session is complete, QuickTest displays a report detailing the results.

You can run the entire test from the beginning, or you can run part of it. You can

designate certain steps as optional, to enable QuickTest to bypass them instead ofaborting the run if these steps do not succeed.

For more information on Executing Tests see chapter 22 of part III, Running Testsof Mercury QuickTest Professional Basic Features Users Guide.

Analyzing Test Results

8/11/2019 QTP_Basic

40/42

22 October 2010

40

Analyzing Test Results

After running a test, you can view a report of major events that occurred during the runsession.

When a run session ends, you can view the run session results in the Test Results

window. By default, the Test Results window opens automatically at the end of a run. If

you want to change this behavior, clear the View results when run session ends checkbox in the Run tab of the Options dialog box.

The Test Results window contains a description of the steps performed during the run

session. For a test that does not contain Data Table parameters, the Test Resultswindow shows a single test iteration.

If the test contains Data Table parameters, and the test settings are configured to run

multiple iterations, the Test Results window displays details for each iteration of the test

run. The results are grouped by the actions in the test.

For more information on Test Result Analization see chapter 23 of part III, Analyzing

Test Results of Mercury QuickTest Professional Basic Features Users Guide.

f

8/11/2019 QTP_Basic

41/42

22 October 2010

41

References / Further Readings:

1.Mercury QuickTest Professional Tutorial

2.Mercury QuickTest Professional Basic Features Users Guide

3.QTP Advanced Features training material (ppt)

4.Mercury QuickTest Professional Advanced Features Users Guide

http://172.20.120.138/epublish$/E%20Publishing/K%20N%20O%20W%20M%20A%20X/P%20R%20O%20D%20U%20C%20T%20I%20ON/KM%20Assets/Program%20Files/Mercury%20Interactive/QuickTest%20Professional/help/QTTutorial.pdfhttp://172.20.120.138/epublish$/E%20Publishing/K%20N%20O%20W%20M%20A%20X/P%20R%20O%20D%20U%20C%20T%20I%20ON/KM%20Assets/Program%20Files/Mercury%20Interactive/QuickTest%20Professional/help/BasicGuide.pdfhttp://172.20.120.138/epublish$/E%20Publishing/K%20N%20O%20W%20M%20A%20X/P%20R%20O%20D%20U%20C%20T%20I%20ON/KM%20Assets/Program%20Files/Mercury%20Interactive/QuickTest%20Professional/help/AdvancedGuide.pdfhttp://172.20.120.138/epublish$/E%20Publishing/K%20N%20O%20W%20M%20A%20X/P%20R%20O%20D%20U%20C%20T%20I%20ON/KM%20Assets/Program%20Files/Mercury%20Interactive/QuickTest%20Professional/help/AdvancedGuide.pdfhttp://172.20.120.138/epublish$/E%20Publishing/K%20N%20O%20W%20M%20A%20X/P%20R%20O%20D%20U%20C%20T%20I%20ON/KM%20Assets/Program%20Files/Mercury%20Interactive/QuickTest%20Professional/help/AdvancedGuide.pdfhttp://172.20.120.138/epublish$/E%20Publishing/K%20N%20O%20W%20M%20A%20X/P%20R%20O%20D%20U%20C%20T%20I%20ON/KM%20Assets/Program%20Files/Mercury%20Interactive/QuickTest%20Professional/help/AdvancedGuide.pdfhttp://172.20.120.138/epublish$/E%20Publishing/K%20N%20O%20W%20M%20A%20X/P%20R%20O%20D%20U%20C%20T%20I%20ON/KM%20Assets/Program%20Files/Mercury%20Interactive/QuickTest%20Professional/help/BasicGuide.pdfhttp://172.20.120.138/epublish$/E%20Publishing/K%20N%20O%20W%20M%20A%20X/P%20R%20O%20D%20U%20C%20T%20I%20ON/KM%20Assets/Program%20Files/Mercury%20Interactive/QuickTest%20Professional/help/QTTutorial.pdf

8/11/2019 QTP_Basic

42/42

22 October 2010

42

Thank You