Qtp Tutorial

Mercury QuickTest Professional
Tutorial
Version 8.0

Mercury QuickTest Professional Tutorial, Version 8.0

This manual, and the accompanying software and other documentation, is protected by U.S. and
international copyright laws, and may be used only in accordance with the accompanying license
agreement. Features of the software, and of other products and services of Mercury Interactive
Corporation, may be covered by one or more of the following patents: U.S. Patent Nos. 5,701,139;
5,657,438; 5,511,185; 5,870,559; 5,958,008; 5,974,572; 6,138,157; 6,144,962; 6,205,122; 6,237,006;
6,341,310; 6,360,332, 6,449,739; 6,470,383; 6,477,483; 6,549,944; 6,560,564; 6,564,342; 6,587,969;
6,631,408; 6,631,411; 6,633,912; 6,694,288; 6,738,813; 6,738,933 and 6,754,701. Other patents
pending. All rights reserved.

Mercury, Mercury Interactive, the Mercury Interactive logo, LoadRunner, LoadRunner TestCenter,
QuickTest Professional, SiteScope, SiteSeer, TestDirector, Topaz and WinRunner are trademarks or
registered trademarks of Mercury Interactive Corporation or its subsidiaries, in the United States
and/or other countries. The absence of a trademark from this list does not constitute a waiver of
Mercury Interactive's intellectual property rights concerning that trademark.

All other company, brand and product names are registered trademarks or trademarks of their
respective holders. Mercury Interactive Corporation disclaims any responsibility for specifying which
marks are owned by which companies or which organizations.

Mercury Interactive Corporation
379 North Whisman Road
Mountain View, CA 94043
Tel: (650) 603-5200
Toll Free: (800) TEST-911
Customer Support: (877) TEST-HLP
Fax: (650) 603-5300

© 2004 Mercury Interactive Corporation, All rights reserved

If you have any comments or suggestions regarding this document, please send them via e-mail to
documentation@mercury.com.

QTPTUT8.0/06

Table of Contents

Welcome to the QuickTest Tutorial ......................................................v
Using This Tutorial ...............................................................................vi
Typographical Conventions................................................................vii
Lesson 1: Introducing QuickTest...........................................................1
Benefits of Automated Testing ..............................................................1
Testing Process.......................................................................................2
QuickTest Window................................................................................4
Mercury Tours Sample Web Site ...........................................................7
Lesson 2: Recording Tests .....................................................................9
Preparing to Record a Test.....................................................................9
Recording a Test ..................................................................................10
Analyzing the Test in the Keyword View............................................15
Lesson 3: Running and Analyzing Tests..............................................19
Running a Test.....................................................................................19
Analyzing Test Results.........................................................................21
Lesson 4: Creating Checkpoints ..........................................................25
Understanding Checkpoint Types ......................................................26
Checking Objects ................................................................................27
Checking Pages....................................................................................31
Checking Text .....................................................................................33
Checking Tables ..................................................................................35
Running and Analyzing a Test with Checkpoints ..............................38
Lesson 5: Parameterizing Tests...........................................................45
Defining a Data Table Parameter ........................................................45
Adding Parameter Values to a Data Table...........................................48
Modifying Steps Affected by Parameterization ...................................49
Running and Analyzing a Parameterized Test ....................................51

iii

Table of Contents

Lesson 6: Creating Output Values.......................................................55
Creating an Output Value ...................................................................55
Running and Analyzing a Test with Output Values ...........................61
Lesson 7: Using Regular Expressions ..................................................63
Regular Expression Syntax ..................................................................63
Working with Regular Expressions .....................................................64
Running and Analyzing a Test with Regular Expressions...................67
Lesson 8: Dividing Tests into Multiple Actions...................................69
Working with Multiple Actions ..........................................................69
Creating New Actions..........................................................................70
Inserting Existing Actions ...................................................................79
Parameterizing an Action ....................................................................84
Running and Analyzing a Multi-action Test.......................................88
Lesson 9: Where Do You Go from Here? ............................................91
Testing Your Own Application—Getting Started ...............................91
Getting Additional Information .........................................................94
Documentation Updates .....................................................................97
Index....................................................................................................99

iv

Welcome to the QuickTest Tutorial

Welcome to the QuickTest tutorial. The tutorial is a self-paced guide that
teaches you the basics of testing your application with QuickTest, Mercury
Interactive’s powerful functional testing tool.

QuickTest enables you to test standard Web objects, ActiveX controls, and
Visual Basic controls.

This tutorial will familiarize you with the process of creating and running
automated tests and analyzing the test results.

Note: In addition to tests, QuickTest enables you to create business
components for use in business process tests, if you have Quality Center
with Business Process Testing support installed. The procedures described in
this tutorial are designed for creating tests, but you can also apply the
majority of these procedures to creating business components. For more
information on business components and Business Process Testing, refer to
the QuickTest Professional User’s Guide and the Business Process Testing User’s
Guide.

This introduction describes:

➤ Using This Tutorial
➤ Typographical Conventions

v

Welcome

Using This Tutorial
The tutorial is divided into nine short lessons. In each lesson you will create
and run tests on the sample Mercury Tours Web site.

After completing the tutorial, you can apply the skills you have learned to
your own Web site.

Lesson 1, Introducing QuickTest compares automated and manual testing
methods. It introduces the QuickTest testing process and familiarizes you
with the QuickTest user interface and the sample Mercury Tours Web site.

Lesson 2, Recording Tests teaches you how to record a test and provides an
overview of the resulting Keyword View display.

Lesson 3, Running and Analyzing Tests shows you how to run a test and
view the test results.

Lesson 4, Creating Checkpoints explains how to add checkpoints to your
test to verify that information in your Web site is displayed as expected.

Lesson 5, Parameterizing Tests shows you how to parameterize your test so
that you can run it on multiple sets of data.

Lesson 6, Creating Output Values teaches you how to use output parameters
to retrieve data from your Web site.

Lesson 7, Using Regular Expressions teaches you how to create and run a
test using regular expressions.

Lesson 8, Dividing Tests into Multiple Actions explains how to divide your
test into actions so that you can design more efficient and modular tests.

Lesson 9, Where Do You Go from Here? shows you how to get started
testing your own Web site and tells you where you can find more
information about QuickTest.

vi

Welcome

Typographical Conventions
This book uses the following typographical conventions:

1, 2, 3 Bold numbers indicate steps in a procedure.
➤ Bullets indicate options and features.
> The greater than sign separates menu levels (for
example, File > Open).
Stone Sans The Stone Sans font indicates names of interface
elements (for example, the Run button) and other
items that require emphasis.
Bold Bold text indicates method or function names.
Italics Italic text indicates method or function arguments, file
names in syntax descriptions, and book titles.
<> Angle brackets enclose a part of a file path or URL
address that may vary from user to user (for example,
<MyProduct installation folder>bin).
Arial The Arial font is used for examples and text that is to
be typed literally.
Arial bold The Arial bold font is used in syntax descriptions for
text that should be typed literally.
... In a line of syntax, an ellipsis indicates that more items
of the same format may be included. In a
programming example, an ellipsis is used to indicate
lines of a program that were intentionally omitted.
[ ] Square brackets enclose optional arguments.
| A vertical bar indicates that one of the options
separated by the bar should be selected.

vii

1
Introducing QuickTest

In this lesson you will learn about the:

➤ Benefits of Automated Testing
➤ Testing Process
➤ QuickTest Window
➤ Mercury Tours Sample Web Site

Benefits of Automated Testing
If you have ever tested applications or Web sites manually, you are aware of
the drawbacks. Manual testing is time-consuming and tedious, requiring a
heavy investment in human resources. Worst of all, time constraints often
make it impossible to manually test every feature thoroughly before the
application is released. This leaves you wondering whether serious bugs
have gone undetected.

Automated testing with QuickTest addresses these problems by dramatically
speeding up the testing process. You can create tests that check all aspects of
your application or Web site, and then run these tests every time your site or
application changes.

1

Lesson 1 • Introducing QuickTest

As QuickTest runs tests, it simulates a human user by moving the mouse
cursor in a Web page or application window, clicking Graphical User
Interface (GUI) objects, and entering keyboard input; however, QuickTest
does this faster than any human user.

Benefits of Automated Testing

Fast QuickTest runs tests significantly faster than human
users.

Reliable Tests perform precisely the same operations each time
they are run, thereby eliminating human error.

Repeatable You can test how the Web site or application reacts after
repeated execution of the same operations.

Programmable You can program sophisticated tests that bring out
hidden information.

Comprehensive You can build a suite of tests that covers every feature in
your Web site or application.

Reusable You can reuse tests on different versions of a Web site or
application, even if the user interface changes.

Testing Process
The QuickTest testing process consists of 7 main phases:

1 Preparing to record
Before you record a test, confirm that your application and QuickTest are set
to match the needs of your test.
Make sure your application displays elements on which you want to record,
such as a toolbar or a special window pane, for example, and that your
application options are set as you expect for the purposes of your test.
You should also view the settings in the Test Settings dialog box (Test >
Settings) and the Options dialog box (Tools > Options) to ensure that
QuickTest will record and store information appropriately. For example, you
should confirm that the test is set to use the appropriate object repository
mode.

2


2 Recording a session on your application
As you navigate through your application or Web site, QuickTest graphically
displays each step you perform as a row in the Keyword View. A step is any
user action that causes or makes a change in your application, such as
clicking a link or image, or entering data in a form.
3 Enhancing your test
➤ Inserting checkpoints into your test lets you search for a specific value of
a page, object, or text string, which helps you determine whether your
application or site is functioning correctly.
➤ Broadening the scope of your test, by replacing fixed values with
parameters, lets you check how your application performs the same
operations with multiple sets of data.
➤ Adding logic and conditional or loop statements enables you to add
sophisticated checks to your test.
4 Debugging your test
You debug a test to ensure that it operates smoothly and without
interruption.
5 Running your test
You run a test to check the behavior of your application or Web site. While
running, QuickTest opens the application, or connects to the Web site, and
performs each step in your test.
6 Analyzing the test results
You examine the test results to pinpoint defects in your application.
7 Reporting defects
If you have Quality Center installed, you can report the defects you discover
to a database. Quality Center is Mercury Interactive’s software test
management tool.

3


QuickTest Window
Before you begin creating tests, you should familiarize yourself with the
main QuickTest window.

The image below shows a QuickTest window as it would appear after you
record a test, with all toolbars and panes (except the Debug Viewer pane)
displayed:

Title bar
Menu bar

File toolbar
Debug
toolbar
Testing
toolbar
Action
toolbar

Test pane

Data
Table

Status bar Active Screen

4


The QuickTest window contains the following key elements:

➤ Title bar—Displays the name of the currently open test.
➤ Menu bar—Displays menus of QuickTest commands.
➤ File toolbar—Contains buttons to assist you in managing your test.
Open Print Data Results Options Object
Table Repository

New Save Active Debug Test Quality Object
Screen Viewer Settings Center Spy
Connection

➤ Testing toolbar—Contains buttons to assist you in the testing process.
Split Start Analog
Record Stop Action Transaction Recording

Start New Insert End Low-Level
Run Action Checkpoint Transaction Recording

➤ Debug toolbar—Contains buttons to assist you in debugging tests.
Step Step Clear All
Into Out Breakpoints

Pause Step Insert/Remove
Over Breakpoint

Note: The Debug toolbar is not displayed when you open QuickTest for the
first time. You can display the Debug toolbar by choosing View > Toolbars >
Debug. Note that this tutorial does not describe how to debug a test. For
additional information, refer to the QuickTest Professional User’s Guide.

5


➤ Action toolbar—Contains buttons and a list of actions, enabling you to view
the details of an individual action or the entire test flow.
Action List Display selected action

Back

Note: The Action toolbar is only displayed in the Keyword View. It is not
displayed when you open QuickTest for the first time. You can display the
Action toolbar by choosing View > Toolbars > Action. If you insert a reusable
or external action in a test, the Action toolbar is displayed automatically in
the Keyword View. For additional information, refer to the QuickTest
Professional User’s Guide.

➤ Test pane—Contains the Keyword View and Expert View tabs.
➤ Active Screen—Provides a snapshot of your application as it appeared when
you performed a certain step during the recording session.
➤ Data Table—Assists you in parameterizing your test.
➤ Debug Viewer pane—Assists you in debugging your test. The Debug Viewer
pane contains the Watch Expressions, Variables, and Command tabs. (The
Debug Viewer pane is not displayed when you open QuickTest for the first
time. You can display the Debug Viewer by choosing View > Debug Viewer.)
➤ Status bar—Displays the status of the QuickTest application.

The buttons used in the File and Testing toolbars are described in detail in
subsequent lessons. The buttons used in the Debug toolbar are described in
detail in the “Debugging Tests” chapter in the QuickTest Professional User’s
Guide. The Action toolbar is described in Lesson 8, “Dividing Tests into
Multiple Actions.”

Note that you can also execute many menu commands using shortcut keys.
For additional information, see the “QuickTest at a Glance” chapter in the
QuickTest Professional User’s Guide.

6


Now that you are familiar with the main QuickTest window, take a few
minutes to explore its components.

Mercury Tours Sample Web Site
Mercury Tours is the sample Web application used throughout this tutorial.
It simulates a Web-based flight information and reservation service. You
should familiarize yourself with this application before starting the tutorial.

Optimizing Browser Settings for Your Test
If you are using Internet Explorer as your browser, you should clear the
option to use AutoComplete for user names and passwords for the purposes
of this tutorial. This will ensure that all of your operations are accurately
recorded while creating your tests.

To clear the AutoComplete option:
1 In your Internet Explorer’s menu bar, choose Tools > Internet Options >
Content tab.
2 Click AutoComplete in the Personal information area. The AutoComplete
Settings dialog box opens.
3 In the Use AutoComplete for area, clear the User names and passwords on
forms option.
4 Click OK to save your changes and close the AutoComplete Settings dialog
box, then click OK again to close the Internet Options dialog box.

Using the Mercury Tours Web Site for the First Time
Before you begin recording your tests on the Mercury Tours Web site, you
must register as a user.

To run Mercury Tours:
1 Launch the Mercury Tours application.
In your Web browser, type the following URL:
http://newtours.mercuryinteractive.com
The Mercury Tours home page opens.

7


2 Register with Mercury Tours.
To log-in and use the Mercury Tours application, you must be a registered
user.
From the home page, click the REGISTER navigation button. The Register
page opens.
In the User Information section at the bottom of the page, enter any user
name and password, and confirm your password. (Other information is not
required.)
Click SUBMIT. Mercury Tours confirms your registration. From this
confirmation page, click the SIGN-ON navigation button to enter the
application. The Sign-on page opens. Enter your registered user name and
password, and click SUBMIT.
The Flight Finder page opens.

3 Explore the Mercury Tours site.
Beginning with the Flight Finder page, follow the on-screen instructions to
get flight information and reserve a flight.
Note that on the Book a Flight page, you do not have to fill out actual
personal or credit card information; just enter the required information
(indicated by red) in the Passengers and Credit Card sections. (You may
enter fictitious information.)

4 End your Mercury Tours session.
When you are done exploring the Mercury Tours application, click the
LOG OUT button on the Flight Confirmation page or the SIGN-OFF link at
the top of any application page.
To sign-in again, simply enter your registered user name and password in
the Sign-on page or in the Mercury Tours home page.

5 Close the Web browser.
You are now ready to begin using this tutorial to create tests on the Mercury
Tours application using QuickTest!

8

2
Recording Tests

As you navigate through your Web site or application, QuickTest records
your steps. These operations are the basis of your test. When you stop
recording, you can see the steps of your newly-created test in a graphical
format in the Keyword View.

In this lesson you will learn about:

➤ Preparing to Record a Test
➤ Recording a Test
➤ Analyzing the Test in the Keyword View

Preparing to Record a Test
Before you begin recording a test, ensure that both your application or Web
site and QuickTest are set to match the needs of your test.

For the purposes of this tutorial, ensure that:

➤ You have registered as a user in the Mercury Tours Web site. For more
information, see “Using the Mercury Tours Web Site for the First Time” on
page 7.
➤ If you are using Internet Explorer as your browser, the AutoComplete option
is cleared for user names and passwords. For instructions, see “Optimizing
Browser Settings for Your Test” on page 7.
➤ All browsers are closed before you begin recording.

9

Lesson 2 • Recording Tests

Recording a Test
In this section, you will record the process of making a reservation for a
flight from New York to San Francisco on the Mercury Tours Web site.

1 Start QuickTest and open a new test.
➤ If QuickTest is not currently open, choose Start > Programs > QuickTest
Professional > QuickTest Professional.
In the Add-in Manager, confirm that the Web Add-in is selected, and
clear all other add-ins. Click OK to close the Add-in Manager and open
QuickTest.

Note: While QuickTest loads your selected add-ins, the QuickTest splash
screen is displayed. This may take a few seconds.

If the Welcome window opens, click Blank Test.
Otherwise, choose File > New, or click the New button.
A blank test opens.

➤ If QuickTest is already open, check which add-ins are loaded by selecting
Help > About QuickTest Professional. If the Web Add-in is not loaded,
you must exit and restart QuickTest. When the Add-in Manager opens,
select the Web Add-in, and clear all other add-ins.
Choose File > New, or click the New button.
A blank test opens.

Note: If the Add-in Manager does not open when starting QuickTest,
choose Tools > Options. In the General tab, select Display Add-in
Manager on startup. When you exit and restart QuickTest, the Add-in
Manager opens.

10


2 Start recording on the Mercury Tours Web site.
Choose Test > Record or click the Record button. The Record and Run

➤ In the Web tab, select Open the following browser when a record or run
session begins.
Choose a browser from the Type list and confirm that the URL in the
Address box is http://newtours.mercuryinteractive.com.
Confirm that Close the browser when the test closes and Do not record
and run on browsers that are already open are selected.

11


➤ In the Windows Applications tab, confirm that Record and run on these
applications (opened on session start) is selected, and that there are no
applications listed.

This setting prevents you from inadvertently recording operations
performed on various Windows applications (such as e-mail) during a
recording session.

Click OK.
QuickTest begins recording, and your browser opens to the Mercury Tours
Web site.

3 Log in to the Mercury Tours Web site.
In the User Name and Password boxes, type the name and password you
registered with Mercury Tours.
Click Sign-In.

12


4 Enter flight details.
Change the following selections:
➤ Departing From: New York
➤ On: Dec 29
➤ Arriving In: San Francisco
➤ Returning: Dec 31
➤ Service Class: Business class
Click CONTINUE to accept the other default selections. The Select Flight
page opens.

Notes:

When selecting the date, you must click on the drop-down list, scroll to any
entry that is not showing, and select it. This is because QuickTest only
records a step if the value in the list changes. The tutorial will not work
correctly if you accept the currently displayed month or day.
When entering dates while recording this test, do not click the View
Calendar button, which opens a Java-based calendar. Your test will not
record the date selected using this calendar because the Java Add-in is not
loaded for this tutorial (The Java Add-in is an external add-in that can be
purchased separately.)
To check which add-ins are loaded, click Help > About QuickTest
Professional. To change the available add-ins for your tests, you must close
and reopen QuickTest Professional.

5 Select a flight.
Click CONTINUE to accept the default flight selections. The Book a Flight
page opens.

6 Enter required passenger and purchase information.
Enter the required information (fields with red text labels) in the Passengers
and Credit Card sections. (You may enter fictitious information.)

13


In the Billing Address section, select Ticketless Travel.
At the bottom of the page, click SECURE PURCHASE. The Flight
Confirmation page opens.

7 Review and complete your booking.
Click BACK TO HOME. The Mercury Tours home page opens.

8 Stop recording.
In QuickTest, click Stop on the Testing toolbar to stop the recording process.
You have now reserved an imaginary business class ticket from New York to
San Francisco. QuickTest recorded your Web browser operations from the
time you clicked the Record button until you clicked the Stop button.

9 Save your test.
Select File > Save or click the Save button. The Save dialog box opens to the
Tests folder.
Create a folder named Tutorial, select it, and click Open.
Type Recording in the File name field.
Confirm that Save Active Screen files is selected.
Click Save. The test name (Recording) is displayed in the title bar of the
main QuickTest window.

14


Analyzing the Test in the Keyword View
As you recorded your test, QuickTest generated steps in the Keyword View
representing each operation you performed in the Web browser.

The columns in the Keyword View show different information for each step,
as follows:

➤ Item—Displays the item for the step (test object, utility object, function call,
or statement) in a hierarchical icon-based tree.
➤ Operation—The operation to be performed on the item, for example, Click
or Select.
➤ Value—The argument values for the selected operation, for example, the
mouse button to use when clicking the image.
➤ Assignment—The assignment of a value to or from a variable so you can use
the value later in the test.
➤ Comment—Any textual information you want to add regarding the step, for
example, Return to page used in first step of the test.
➤ Documentation—Auto-documentation of what the step does, in an
easy-to-understand sentence, for example, Click the “findFlights” image.

Note: You can choose to hide or display individual columns as required, by
right-clicking the column heading in the Keyword View and selecting a
column name from the list.

In the Item column of the Keyword View, you can click the branch arrows to
expand or collapse the steps under each Web page. You can expand the
entire test by choosing View > Expand All.

15


When you expand your test, it should look similar to this:

For every step performed on an object, QuickTest displays a row in the
Keyword View with an icon and details of the step. For example, the step
below instructs QuickTest to click the reserveFlights image at a specific
location in the Select a Flight: Mercury page of the Mercury Tours Web site.

16


The table below provides an explanation of the first few steps shown in the
test in the Keyword View above.

Step Description

Action1 is the action name.

The browser invokes the Welcome:
Mercury Tours Web site.

Welcome: Mercury Tours is the name
of the Web page.

userName is the name of the edit box.
Set is the method performed on the
edit box. mercury is the value of the
edit box.

password is the name of the edit box.
SetSecure is an encryption method
performed on the edit box.
4082820183afe512e8bc91c1f7222dbd
is the encrypted value of the password.

Sign-In is the name of the image link.
Click is the method performed on the
image. 2, 2 are the x- and y-coordinates
where the image was clicked.

Take a few minutes to examine the Keyword View in detail, tracing the steps
you performed while recording your test.

For more information on the Keyword View, refer to the QuickTest

17


18

3
Running and Analyzing Tests

When you run your test, QuickTest opens the appropriate application or
Web site and performs each step as it was originally recorded in the test.
When QuickTest finishes running the test, it displays the results of the run.


➤ Running a Test
➤ Analyzing Test Results

Running a Test
In this lesson, you will run the test you recorded in the previous lesson.

1 Start QuickTest and open the Recording test.
If QuickTest is not already open, choose Start > Programs > QuickTest
➤ If the Welcome window opens, click Open Existing.
➤ If QuickTest opens without displaying the Welcome window, choose
File > Open or click the Open button.
In the Open Test dialog box, locate and select the Recording test, then click
Open.

19

Lesson 3 • Running and Analyzing Tests

2 Confirm that all images are saved to the test results.
QuickTest allows you to determine when to save images to the test results.
In this lesson, all images should be saved to the test results.
Choose Tools > Options and select the Run tab. In the Save step screen
capture to test results option, select Always.
Click OK to close the Options dialog box.

3 Start running your test.
Click Run or choose Test > Run. The Run dialog box opens.
Select New run results folder. Accept the default results folder name.
Click OK to close the Run dialog box.

Watch carefully as QuickTest opens your browser and starts running the test.
In the browser, you can see QuickTest perform each step you recorded; a
yellow arrow in the left margin of the Keyword View indicates the step that
QuickTest is running.

20


Analyzing Test Results
When QuickTest finishes running the test, the Test Results window opens.

Results tree

Test results details

Iteration summary

Status summary

21


Initially, the Test Results window contains two panes for displaying the key
elements of your test run.
➤ The left pane displays the results tree, an icon-based view of the steps
that were performed while the test was running. The results tree is
organized according to the Web pages visited during the test run and can
be expanded (+) to view each step. The steps performed during the test
run are represented by icons in the tree. You can instruct QuickTest to
run a test or action more than once using different sets of data in each
run. Each test run is called an iteration, and each iteration is numbered.
(The test you ran had only one iteration.)
➤ The right pane displays the test results details. The iteration summary
table indicates which iterations passed and which failed. The status
summary table indicates the number of checkpoints or reports that
passed, failed, and raised warnings during the test.
Your test run succeeded because QuickTest was able to navigate the Mercury
Tours site just as the test was originally recorded. In this section, you will
inspect the steps QuickTest performed when running your test, and how the
application window appeared when a step was performed.

1 View the test results for a specific step.
In the results tree, expand (+) Test Recording Summary >
Recording Iteration 1 (Row 1) > Action1 Summary > Welcome Mercury
Tours > Find a Flight.

22


Highlight "fromPort":Select "New York" in the results tree.

Results tree

Test results details

Active Screen
image

The Test Results window now contains three panes, displaying:
➤ the results tree, with one step highlighted
➤ the test results details of the highlighted step
➤ the Active Screen, showing a screen capture of the Web page on which
the step was performed.

23


When you click a page in the results tree, QuickTest displays the
corresponding page in the application view. When you click a step (an
operation performed on an object) in the results tree, the corresponding
object is highlighted in the application view. In this case, the Departing
From text box is highlighted.

2 Close the Test Results window.
Choose File > Exit.
You have now successfully created and run a test that reserves a flight from
New York to San Francisco on the Mercury Tours Web site.

24

4
Creating Checkpoints

In the previous lessons, you created and ran a test checking that a series of
steps performed on the Mercury Tours Web site runs smoothly. A checkpoint
verifies that expected information is displayed in your application while the
test is running.


➤ Understanding Checkpoint Types
➤ Checking Objects
➤ Checking Pages
➤ Checking Text
➤ Checking Tables
➤ Running and Analyzing a Test with Checkpoints

25

Lesson 4 • Creating Checkpoints

Understanding Checkpoint Types
QuickTest Professional offers the following types of checkpoints:

Checkpoint
Description Example of Use
Type

Standard Checks values of an object’s Check that a radio button is
Checkpoint properties. selected.

Image Checks the property values of Check that the image source file
Checkpoint an image. is correct.

Table Checks information in a table. Check that the value in a table
Checkpoint cell is correct.

Page Checks the characteristics of a Check how long a Web page takes
Checkpoint Web page. to load or if a Web page contains
broken links.

Text / Checks that a text string is Check whether the expected text
Text Area displayed in the appropriate string is displayed in the expected
Checkpoint place in a Web page or location on a Web page or dialog
application window. box.

Bitmap Checks an area of a Web page or Check that a Web page (or any
Checkpoint application after capturing it as portion of it) is displayed as
a bitmap expected.

Database Checks the contents of Check that the value in a
Checkpoint databases accessed by an database query is correct.
application or Web site

Accessibility Identifies areas of a Web site to Check if the images on a Web
Checkpoint check for Section 508 page include ALT properties,
compliancy. required by the W3C Web
Content Accessibility Guidelines.

XML Checks the data content of Note: XML file checkpoints are
Checkpoint XML documents. used to check a specified XML
file; XML application checkpoints
are used to check an XML
document within a Web page.

26


You can add most checkpoints to your test either while recording or
afterward. The following sections explain how to create some of the
checkpoints described above on the test you created in “Recording Tests” on
page 9.

Note: When QuickTest creates a checkpoint, it assigns a name based on
information inside the checkpoint—the checked value, for example. The
checkpoint name remains unchanged, even if you subsequently modify the
information on which it was based. Keep this in mind when looking for
checkpoints displayed in the Keyword View. However, note that QuickTest
may shorten the name displayed in the Keyword View.

For more information on how to create checkpoints, refer to the QuickTest

Checking Objects
In this section, you will add a standard checkpoint in the Book a Flight page.
This checkpoint will verify the value in the box containing the first name of
the passenger.

Open.

2 Save the test as Checkpoint.
Select File > Save As. Save the test as Checkpoint.

27


3 Confirm that the Active Screen option is enabled.
If you do not see the Active Screen at the bottom of the QuickTest window,
click the Active Screen button, or choose View > Active Screen.

4 Locate the page where you want to add a standard checkpoint.
You want to add a checkpoint that checks the property values of the First
Name edit box after the passenger’s name has been entered in the box.
In the Item column of the Keyword View, expand (+) Action1 > Welcome:
Mercury Tours > Book a Flight: Mercury.
The Book a Flight page is displayed in the Active Screen and the object
corresponding to the selected step is highlighted. You can see that the
passenger’s first name is displayed in the First Name box.

5 Create a standard checkpoint.
In the Active Screen, right-click the First Name box and choose Insert
Standard Checkpoint. The Object Selection – Checkpoint Properties dialog
box opens.

Confirm that WebEdit: passFirst0 is highlighted, and click OK.

28


The Checkpoint Properties dialog box opens.

The dialog box displays the object’s properties:
➤ The Name is the name of the object as defined in the HTML code of the
Web page.
➤ The Class is the type of object. WebEdit indicates that the object is an
edit box.
➤ The ABC icon in the type column indicates that the value of the property
is a constant.

29


For each object class, QuickTest recommends default property checks. The
table below describes the default checks.

Property Value Explanation

html tag INPUT INPUT is the html tag as defined in the
HTML source code.

innertext In this case, the value of innertext is
empty. The checkpoint checks that the
value is empty.

name passFirst0 passFirst0 is the name of the edit box.

type text text is the type of object as defined in the
HTML source code.

value <FirstName> The value entered in the edit box.
(The name you entered
while recording)

The first name is entered in the First Name box when the passFirst0 Set...
step is performed. Therefore, in the Insert statement area of the Checkpoint
Properties dialog box, select After current step. This inserts the checkpoint
after the passFirst0 Set... step in which the first name is entered.

Accept the rest of the settings as default and click OK. QuickTest adds a
standard checkpoint step to your test below the selected step.

6 Save the test.
Choose File > Save or click the Save button.

You insert most checkpoints in the manner described above. Several special
types of checkpoints are explained in the following sections.

30


Checking Pages
In this section, you will add a page checkpoint to your test. The page
checkpoint checks that the number of links and images in the page when
you run your test is the same as when you recorded your test.

1 Locate the page where you want to add a page checkpoint.
In the Keyword View, expand (+) Action1 > Welcome: Mercury Tours.
Highlight the Book a Flight: Mercury row in the Keyword View. The page is
displayed in the Active Screen.

2 Create a page checkpoint.
Right-click anywhere in the Active Screen, and choose Insert Standard
Checkpoint. The Object Selection – Checkpoint Properties dialog box opens.
Note that this dialog box may include different elements, depending on
where you click in the Active Screen.
Highlight Page: Book a Flight: Mercury (the top level) and click OK.

31


The Page Checkpoint Properties dialog box opens.

When you run the test, QuickTest checks the number of links and images in
the page and the load time, as described in the pane at the top of the dialog
box.
QuickTest also checks the actual target URL of each link and the actual
source of each image.
Accept the default settings and click OK.

32


QuickTest adds the page checkpoint to your test. It is displayed in the
Keyword View as a checkpoint operation on the Book a Flight: Mercury
page.

3 Save the test.

Checking Text
In this section, you will add a text checkpoint to your test to check whether
New York is displayed in the Flight Confirmation page.

1 Locate the page where you want to add a text checkpoint.
Highlight the Flight Confirmation: Mercury page in the Keyword View. The
page is displayed in the Active Screen.

2 Create a text checkpoint.
In the Active Screen, under “Departing,” highlight the text New York.

33


Right-click the highlighted text and choose Insert Text Checkpoint. The Text
Checkpoint Properties dialog box opens.

When Checked Text appears in the list box, the Constant field displays the
text string you highlighted. This is the text QuickTest looks for when
running the test.
Click OK to accept the default settings in this dialog box.
QuickTest adds the text checkpoint to your test. It is displayed in the
Keyword View as a checkpoint operation on the
Flight Confirmation: Mercury page.

3 Save the test.

34


Checking Tables
In this section, you will add a table checkpoint to check the cost of the
outbound flight, as displayed in the Book a Flight: Mercury page.

1 Locate the page where you want to add a table checkpoint.
In the Keyword View, expand (+) Welcome: Mercury Tours >
Book a Flight: Mercury.
Highlight the passFirst0 step in the Keyword View. The page is displayed in
the Active Screen.

2 Create a table checkpoint.
In the Active Screen, right-click the price displayed for the first flight (New
York to San Francisco)—270—and choose Insert Standard Checkpoint.
The Object Selection – Checkpoint Properties dialog box opens.
Select WebTable: New York to San Fransisco.

Note that the table you selected is highlighted in the Active Screen. Click
OK.

35


The Table Checkpoint Properties dialog box opens, showing the rows and
columns of the table.

Note that by default, check marks appear in all cells. You can double-click a
cell to toggle the cell selection, or double-click a row or column header to
toggle the selection for all the cells in the selected row or column.

36


Double-click each column header to clear the check marks. Double-click
column 3, row 3 to check the value of this cell. (QuickTest checks only cells
containing check marks.)

Tip: You can change the column widths and row heights by dragging the
boundaries of the column and row headers.

Click OK to close the dialog box.
QuickTest adds the table checkpoint to your test. It is displayed in the
Keyword View as a new step under the Book a Flight: Mercury page.

3 Save the test.

37


Running and Analyzing a Test with Checkpoints
In this section, you will review your test with checkpoints, run the test, and
analyze the checkpoint results.

1 Expand the test and review your test.
Choose View > Expand All or use the * shortcut key on your number keypad.
The Keyword View displayed is similar to the following:

Page checkpoint
Table checkpoint

Standard
checkpoint

Text checkpoint

38


2 Start running your test.
Click Run or choose Test > Run. The Run dialog box opens. Ensure that New
run results folder is selected. Accept the default results folder name.
Click OK. When the test run is completed, the Test Results window opens.

3 View the test results.
When QuickTest finishes running the test, the Test Results window opens.
The test result should be Passed, indicating that all checkpoints passed. If
one or more checkpoints had failed, the test result would be Failed.

4 View the results of the page checkpoint.
In the results tree, expand (+) Checkpoint Iteration 1 (Row 1) >
Action1 Summary > Welcome: Mercury Tours > Book a Flight: Mercury.
Highlight Checkpoint “Book a Flight: Mercury”.
In the Details pane, you can review the details of the page checkpoint,
which lists the items checked.

Tip: You can drag the bottom of the Details pane to enlarge it and/or scroll
within the pane to view all of the checkpoint details.

39


The checkpoint passed because the actual values of the checked properties
match the expected values.

5 View the results of the table checkpoint.
In the results tree, Book a Flight: page, expand (+) New York to San
Francisco.
Highlight Checkpoint "New York to San Francisco".
In the Details pane, you can review the details of the table checkpoint. You
can also review the values of the table cells (cell values that were checked are
displayed in black; cell values that were not checked are displayed in gray).

40


The checkpoint passed because the actual value of the checked cell matches
the expected value.

6 View the results of the standard checkpoint.
In the results tree, Book a Flight: Mercury page, expand (+) passFirst0.
Highlight Checkpoint "passFirst0".

41


In the Details pane, you can review the details of the standard checkpoint,
which lists the properties that were checked and their values. The
checkpoint passed because the actual values of the checked properties
match the expected values.

7 View the results of the text checkpoint.
In the results tree, expand (+) Checkpoint Iteration 1 (Row 1) >
Action1 Summary > Welcome: Mercury Tours>
Flight Confirmation: Mercury.
Highlight Checkpoint "New York".

42


In the Details pane, you can review the details of the text checkpoint. The
checkpoint passed because the actual text matches the expected text.

Choose File > Exit.

43


44

5
Parameterizing Tests

When you test your applications, you may want to check how the
application performs the same operations with multiple sets of data. For
example, suppose you want to check how your Web site responds to ten
separate sets of data. You could record ten separate tests, each with its own
set of data. Alternatively, you can create Data Table parameters so that your
test runs ten times, each time using a different set of data.


➤ Defining a Data Table Parameter
➤ Adding Parameter Values to a Data Table
➤ Modifying Steps Affected by Parameterization
➤ Running and Analyzing a Parameterized Test

Defining a Data Table Parameter
In the previous lessons, you reserved a flight from New York to San
Francisco. New York is a constant value, which means that New York is the
departure city each time you run the test. In this exercise you will make the
departure city a parameter so that you can use a different departure city for
each test run.

45

Lesson 5 • Parameterizing Tests

1 Start QuickTest and open the Checkpoint test.
In the Open Test dialog box, locate and select the Checkpoint test, then click
Open.

2 Save the test as Parameter.
Select File > Save As. Save the test as Parameter.


4 Confirm that the Data Table option is enabled.
If you do not see the Data Table at the bottom of the QuickTest window,
click the Data Table button, or choose View > Data Table.
5 Select the text to parameterize.
In the Keyword View, expand (+) Action1 > Welcome: Mercury Tours >
Find a Flight: Mercury.

46


In the fromPort row in the Keyword View, click in the Value cell and then
click the parameterization icon . The Value Configuration Options dialog
box opens.

6 Set the parameterization properties.
Select the Parameter radio button. This lets you replace the constant value
(New York) with a parameter.
Confirm that the DataTable option is selected. This means that the value of
the parameter will be taken from the QuickTest Data Table.
The Name box is enabled and displays p_Item. Change this to departure.

47


Click OK to close the dialog box. QuickTest adds the departure parameter to
the Data Table as a new column and inserts New York in the first row under
it. New York will be the first of several departure cities that QuickTest will
use during test runs of the application.

New column in
Data Table

Note the change in the step’s appearance in the Keyword View. Previously,
the step was displayed as fromPort Select New York. Now, the step is
displayed as fromPort Select DataTable(“departure”, DTGlobalSheet). When
you click the Value cell, the following information is displayed, indicating
that the value is parameterized using a Data Table parameter called
departure:

Adding Parameter Values to a Data Table
As you saw, QuickTest displays parameter values in the Data Table. In this
section, you will add two more departure cities to the Data Table, so that
QuickTest can test the application with this data.

1 Enter additional cities in the departure column.
Click row 2 in the departure column and type Portland.
Click row 3 and type Seattle.
Press Enter.

48


2 Save the test.
Select File > Save or click the Save button.

Modifying Steps Affected by Parameterization
After parameterizing one step in a test, other test objects might be affected
when the value of the parameterized step changes. If so, you must modify
the expected values of those objects to match the value resulting from the
parameterized step. In this section, you will modify the text checkpoint so
that when running the test, QuickTest checks for the text that matches the
current departure city.

1 Locate the text checkpoint to modify.
In the Keyword View, expand (+) Welcome: Mercury Tours.
Right-click Flight Confirmation: Mercury and select Checkpoint Properties.
The Text Checkpoint Properties dialog box opens.

49


2 Parameterize the text checkpoint.
In the Checked Text area, New York is displayed in the Constant box. New
York is the expected value for the checkpoint for every iteration.
Select Parameter and click the Parameter Options button. The Parameter
Options dialog box opens.

In the Name box, select departure. This instructs the checkpoint to use the
departure parameter values in the Data Table for the expected results.
Click OK to close the Parameter Options dialog box, and then click OK again
to close the Text Checkpoint Properties dialog box. The checkpoint is now
parameterized.

3 Save the test.

50


Running and Analyzing a Parameterized Test
You will now run the modified Parameter test. QuickTest will run the test
three times, once for each departure city in the Data Table. Each test run is
called an iteration.

1 Run the Parameter test.
Click Run on the Testing toolbar or choose Test > Run. The Run dialog box
opens.
Select New run results folder and accept the default results folder name.

2 Examine the results summary.
The Test Results window shows that the second and third iterations of the
test failed, even though the text checkpoint passed in all three iterations.
See below for further information about why the iterations failed.
➤ Iteration 2:
In the results tree, expand (+) Parameter Iteration 2 > Action1 Summary
> Welcome Mercury Tours > Flight Confirmation: Mercury.

51



The checkpoint results in the Details pane show that Portland was the
expected result and the actual result. Therefore, the checkpoint passed.
You can also see, in the Application pane, that the flight information
reflects the flight from Portland.

➤ Iteration 3:
In the results tree, expand (+) Parameter Iteration 3 > Action1 Summary
> Welcome Mercury Tours > Flight Confirmation: Mercury.
The checkpoint results in the Details pane show that Seattle was the
expected result and the actual result. Therefore, the checkpoint passed.
The Application pane shows the flight information for the flight from
Seattle.

52


The table below summarizes the results of the text checkpoint in each
iteration:

Iteration Expected Text Actual Text Result

#1 New York New York Checkpoint Passed

#2 Portland Portland Checkpoint Passed

#3 Seattle Seattle Checkpoint Passed

Note: Although the text checkpoints passed in all three iterations, the
second and third iterations of the test still failed because the table
checkpoint failed in these iterations—the ticket price changed when the
departure city changed. In the next lesson, you will modify the table
checkpoint so that when you run your test, QuickTest will update the
expected ticket price in the checkpoint with the correct ticket price for
the current departure city.

Choose File > Exit to close the Test Results window.

53


54

6
Creating Output Values

In the previous lesson, you created parameters that inserted different data
into each iteration of a test run. You can also retrieve data from your
application and output it to the Data Table, using output values. This data
can then be used at a later stage in the test. QuickTest displays the retrieved
data, following the test run, in the Runtime Data Table.

For example, you can use an output value to verify that the date or flight
number is correctly displayed in two different Web pages, by using the value
obtained in one page as the expected text that QuickTest checks for in the
other page.


➤ Creating an Output Value
➤ Running and Analyzing a Test with Output Values

Creating an Output Value
In the previous lesson, the second and third iterations of your test failed
because the ticket price changed when the departure city changed. The
checkpoint that checked the fare of the outbound flight in the Book a
Flight: Mercury page did not update its expected value as the fare changed.

In this lesson, you will create an output value that retrieves the outbound
fare from the Select a Flight: Mercury page in each test iteration. You will
then modify the table checkpoint you created, so that it checks that the
price displayed in the Book a Flight: Mercury page matches the price
captured in the Select a Flight: Mercury page.

55

Lesson 6 • Creating Output Values

1 Start QuickTest and open the Parameter test.
In the Open Test dialog box, locate and select the Parameter test, then click
Open.

2 Save the test as Output.
Select File > Save As. Save the test as Output.


4 Select the text you want to use as an output value.
In the Keyword View, expand (+) Welcome: Mercury Tours and click the
Select a Flight: Mercury page. The page is displayed in the Active Screen.

56


In the Active Screen, highlight the fare, without the $ sign, for the
outbound flight (New York to San Francisco)—270. Right-click the
highlighted text and select Insert Text Output. The Text Output Value
Properties dialog box opens.

57


5 Set the output value settings.
Click the Modify button to open the Output Options dialog box.

The Name box displays Select_a_Flight_MercuryOutput_Text_out. Change
this to depart_flight_price.
Click OK to accept the other default settings and close the Output Options
dialog box. Click OK again to close the Text Output Value Properties dialog
box. QuickTest adds the depart_flight_price column to the Data Table.
QuickTest adds the output value operation to the Select a Flight: Mercury
page in the Keyword View.

6 Modify the table checkpoint that checks the ticket price displayed in
the flight Summary table.
In the Keyword View, expand (+) Welcome:Mercury Tours >
Book a Flight: Mercury.
Right-click Checkpoint "New York to San Francisco", and select Checkpoint
Properties. The Table Checkpoint Properties dialog box opens.

58


Click column 3 in row 3 (the checked cell). In the Configure value area,
select Parameter and click the Parameter Options button. The Parameter
Options dialog box opens.

In the Name box, select depart_flight_price.

59


Click OK to close the Parameter Options dialog box. The Table Checkpoint
Properties dialog box is redisplayed, with a parameterization icon next to
the table value you parameterized.

Parameterized value

Click OK to close the Table Checkpoint Properties dialog box. The
checkpoint is now parameterized.

7 Save the test.

60


Running and Analyzing a Test with Output Values
You will now run the test and examine the results.

1 Run the Output test.
Click the Run button or choose Test > Run. The Run dialog box opens.

2 Examine the run-time data results.
In the Test Results window, select Run-Time Data from the results tree. The
output values used during the test run are displayed in a grid. Note that a
different price is shown in the depart_flight_price column for each
iteration.

3 Examine the checkpoint results.
Choose View > Expand All.
In Output Iteration 1 (Row 1), under the Book a Flight: Mercury page, click
Checkpoint "New York to San Francisco".

61


Note that in the Details pane, the checkpoint is marked in green as passed
because the price of the ticket for the first flight in the Summary table
matched the expected value obtained from the Select a Flight page.
Examine the checkpoints for Iterations 2 and 3 as well. In the Details pane,
these checkpoints are also marked in green as “Passed,” for the same reason.


62

7
Using Regular Expressions

In Lesson 4, “Creating Checkpoints,” you created a text checkpoint that
searched for a specific text string. You can use regular expressions to increase
the flexibility and adaptability of your tests.


➤ Regular Expression Syntax
➤ Working with Regular Expressions
➤ Running and Analyzing a Test with Regular Expressions

Regular Expression Syntax
Regular expressions enable QuickTest to identify objects and text strings
with varying values. You can use regular expressions when defining the
properties of an object, the methods of an argument, when parameterizing a
step, and when creating checkpoints with varying values.

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 define the conditions of the search. For more information
on regular expression syntax, refer to the QuickTest Professional User’s Guide.

63

Lesson 7 • Using Regular Expressions

Working with Regular Expressions
In this tutorial, you will create a text checkpoint on a date text string that
changes according to the selected flight date. You can define the date as a
regular expression so that the checkpoint checks that the captured text
string matches the expected format, rather than checking the exact text.

To do this, you will create a text checkpoint with a regular expression that
will match any single character within a defined range.

Open.

2 Save the test as RegExpression.
Select File > Save As. Save the test as RegExpression.


4 Select the text for which you will create the checkpoint.
In the Keyword View, expand (+) Welcome: Mercury: Tours and click the
Select a Flight: Mercury page. The page is displayed in the Active Screen.
In the Active Screen, scroll up and highlight the date for the outbound
flight, New York to San Francisco (12/29/2004). Right-click the highlighted
string and select Insert Text Checkpoint. The Text Checkpoint Properties
dialog box opens.

64


5 Enter the regular expression for the text you want to check.
In the Checked Text area, click the Constant Value Options button. The
Constant Value Options dialog box opens.

In the Value box, replace the current date with [0-1][0-9]/[0-3][0-9]/200[0-9].
This instructs QuickTest to check that each character in the selected text
matches the number-range format defined by the regular expression. The
expression checks for the following format: MM/DD/200Y.
Select the Regular expression check box. A message box prompts you to
insert the backslash character before each special character. Click No.

Note: Clicking Yes would cause QuickTest to treat the special characters
( [ ), ( - ) and ( ] ) as literal characters and not as a regular expression.

65


Click OK to accept the other default settings and close the Constant Value
Options dialog box. The Text Checkpoint Properties dialog box opens.

Click OK to close the Text Checkpoint Properties dialog box.
QuickTest adds the text checkpoint to your test. It is displayed as a check
operation on the Select a Flight: Mercury page in the Keyword View.

6 Save the test.

66


Running and Analyzing a Test with Regular Expressions
In this exercise you will run the test and examine the checkpoint results.

1 Run the RegExpression test.
Click the Run button or choose Test > Run. The Run dialog box opens.

2 Examine the checkpoint results.
In the results tree, expand (+) Test RegExpression Summary >
RegExpression Iteration 1 (Row 1) > Action1 Summary >
Welcome: Mercury Tours > Select a Flight: Mercury
Select CheckPoint "[0-1][0-9]/[0-3][0-9]/200[0-9]".

67


The checkpoint passed because the text was displayed in the format
specified by the regular expression.

3 Exit the Test Results window.

68

8
Dividing Tests into Multiple Actions

Actions divide your test into logical sections. When you create a new test, it
contains a call to one action. By dividing your tests into calls to multiple
actions, you can design more modular and efficient tests.


➤ Working with Multiple Actions
➤ Creating New Actions
➤ Inserting Existing Actions
➤ Parameterizing an Action
➤ Running and Analyzing a Multi-action Test

Working with Multiple Actions
If you examine one of the tests you created in the previous lessons, you will
see that it can be divided into several distinct processes:

➤ You logged into the Mercury Tours site.
➤ You submitted a flight order.
➤ You logged out.
Assume that you wanted to run your test for five different flight orders. As
we saw in Lesson 5, “Parameterizing Tests”, you could parameterize your test
so that it would run the test five times using five different sets of data. You
can also organize your test so that only the second procedure runs five
times, simulating a single user logging in, ordering five flights, and logging
out. You do this by dividing your test into calls to different actions.

69

Lesson 8 • Dividing Tests into Multiple Actions

To divide your test into calls to different actions, you can insert a call to a
new action, split an existing action into calls to two actions, insert a call to a
copy of an existing action, or insert a call to an existing action.

You can insert calls to actions into your test during your recording session or
afterwards. Use one of the following menu options or toolbar buttons to add
actions to your test:

➤ Insert > Call to New Action or use the Insert Call to New Action button.
➤ Step > Split Action or use the Split Action button.
➤ Insert > Call to Copy of Action or right-click an action and choose Insert Call
to Copy of Action.
➤ Insert > Call to Existing Action or right-click an action and choose Insert Call
to Existing Action.

Creating New Actions
In this exercise you will create a test and divide it into three action calls.

Recording the Test
1 Start QuickTest and open a new test.
For more information, see step 1 of “Recording a Test” on page 10.

2 Start recording on the Mercury Tours Web site.
In the coming steps, you will record a test similar to the one recorded in the
“Recording Tests” lesson. However, this test is designed slightly differently
to optimize the test for a multi-action test.
Confirm that all Web browsers are closed.

70


Choose Test > Record or click the Record button. The Record and Run

➤ In the Web tab, select Open the following browser when a record or run
session begins.
Choose a browser from the Type list and confirm that the URL in the
Address box is http://newtours.mercuryinteractive.com.
Confirm that the Do not record and run on browsers that are already
open and Close the browser when the test is closed options are selected.

➤ In the Windows Applications tab, confirm that Record and run on these
applications (opened on session start) is selected, and that there are no
applications listed.

Click OK.
QuickTest begins recording, and your browser opens to the Mercury Tours
Web site.

71


3 Sign in to the Mercury Tours Web site.
In the User Name and Password boxes, type the name and password you
registered with Mercury Tours.
Click Sign-In.

4 Enter flight details.
Change the following selections:
➤ Departing From: New York
➤ On: Dec 29
➤ Arriving In: San Francisco
➤ Returning: Dec 31
Click CONTINUE to accept the other default selections. The Select Flight
page opens.

5 Select a flight.
Click CONTINUE to accept the default flight selections. The Book a Flight
page opens.

6 Enter required passenger and purchase information.
Enter the required information (fields with red text labels) in the Passengers
and Credit Card sections.
At the bottom of the page, click SECURE PURCHASE. The Flight
Confirmation page opens.

7 Return the browser to the Flight Finder page.
At the bottom of the Flight Confirmation page, click BACK TO FLIGHTS
button. The Flight Finder page opens.
Ending the recording on the Flight Finder page enables you to create an
action that starts and ends on the same page, so that you can call the action
multiple times if you wish.

72


8 Stop Recording.
In QuickTest, click Stop to stop the recording process.

9 Save the test as ActionA.
Select File > Save As. Save the test as ActionA.

Dividing the Test into Two Actions
Since your test currently contains two main processes: signing-in and
purchasing a flight, it makes sense to divide the test into separate actions.

1 Select the page where you want the second action to begin.

2 Split the test into two actions.
Select the first Find a Flight: Mercury page and choose Step > Split Action or
click the Split Action button. The Split Action dialog box opens.

73


3 Enter names and descriptions for the two actions.
In the Name box of the 1st action type: Sign_in.
In the Description box of the 1st action, type: Enters user name and
password to sign in.
In the Name box of the 2nd action type: FlightOrder.
In the Description box of the 2nd action, type: Chooses and purchases a
flight.
Click OK to close the Split Action dialog box and accept the other default
selections. The two actions are displayed in the Keyword View.
Choose View > Expand All to examine the contents of each action. Note that
the FlightOrder action begins and ends with the Find a Flight: Mercury page.

Inserting a Call to a New Action
Now you will insert a call to a new action and record the step of returning to
the Mercury Tours home page so that the entire test begins and ends on the
same page.

1 Insert the ReturnHome action.
Choose Insert > Call to New Action or click the Insert Call to New Action
button. The Insert Call to New Action dialog box opens.

74


Enter ReturnHome in the Name box, confirm that At the end of the test is
selected, and click OK. The dialog box closes and the ReturnHome action is
added to the end of your test.

2 Prepare the application for recording.
Confirm that your Web browser is open to the Flight Finder page.
If your browser is not open, open it to the Mercury Tours site
(http://newtours.mercuryinteractive.com) and sign in. The Flight Finder page
opens.
Position the applications on your desktop so that you can see both
QuickTest and the Web browser.

3 Change the Record and Run settings.
Currently, your Record and Run settings are set so that a new browser opens
each time you begin recording your test. However, because you want to
record a step on a browser that you have already opened and prepared, you
need to change the Record and Run settings before you begin recording.

75


In QuickTest, choose Test > Record and Run Settings. The Record and Run

In the Web tab, select Record and run test on any open Web browser and
click OK.

4 Record the ReturnHome action.
In the Keyword View, select the new ReturnHome action icon.
Choose Test > Record or click the Record button.
Click the Home navigation link on the left side of the Flight Finder page.
The Mercury Tours home page opens.
In QuickTest, click Stop to stop the recording process.

76


5 Return the Record and Run Settings to their original settings.
You changed the record and run settings for the purposes of recording the
ReturnHome action, but this change also affects the way QuickTest runs the
test. You want QuickTest to open a new browser to the Mercury Tours home
page when you run the test, so you need to reapply the original settings.
Choose Test > Run and Record Settings. The Record and Run Settings dialog
box opens.
In the Web tab, select Open the following browser when a record or run
session begins. Confirm that http://newtours.mercuryinteractive.com is
displayed in the Address box and click OK.

6 Save the test.

Setting Actions as Reusable Actions
Reusable actions are like functions in programming. When you have a
process that you may need to include in several tests, you record, modify,
and enhance the steps of the process and save them in a reusable action.
Then you can call the action from other tests, rather than recording,
modifying, and enhancing the same steps each time.

To call an action from another test, you must make it a reusable action in
the test with which it was stored. The Sign_in and ReturnHome action you
created in this lesson can apply to almost any test you might create on the
Mercury Tours site, so it makes sense to make them reusable actions.

77


1 Make the Sign_in action reusable.
In the Keyword View, right-click the Sign_in action and choose Action
Properties. The Action Properties dialog box opens. Select the Reusable
action check box and click OK. If a message box is displayed, read the
message, click Do not show this dialog box again, and click OK. The action
icon changes to a reusable action icon .
2 View the details of the Sign_in action.
Note that you no longer have the option to expand the Sign_in action
within the Keyword View.
If the Action List was not previously displayed above the Keyword View, it is
displayed after you convert the action to a reusable action. The Action List
displays a list of all reusable and external actions in the test.

View the details of the Sign_in action by selecting Sign_in from the Action
List. The details of the Sign_in action are displayed.
In the Action List, select Test Flow to return to the main flow of the test in
the Keyword View.

3 Make the ReturnHome action reusable.
Repeat steps 1 and 2 for the ReturnHome action.

4 Save the test.

78


Inserting Existing Actions
When you plan a suite of tests, you may realize that each test requires one or
more identical activities, such as signing in. Once you have created the
action and stored it with one test, you can insert either a call to a copy of
the existing action, or a call to the existing action, into other tests.

When you insert a call to copy of an existing action, you can make changes
to the copied action, and your changes will neither affect, nor be affected
by, any other test. Calls to existing actions, however, are read-only in the
calling test. They can be modified only in the test with which they were
stored. Calls to existing actions enable you to call the same action from
several tests and make it easy to maintain tests, because when your
application changes you only have to update the existing action stored with
the original test.

In the following exercises you will create a new test that is similar to the
ActionA test, except that the Sign_in and ReturnHome actions are external
actions (calls to existing actions stored with other tests) and the FlightOrder
action is slightly modified.

Inserting Calls to Actions
First, you will insert calls to the reusable Sign_in and ReturnHome actions
from ActionA into ActionB.

1 Open a new test.
For more information, see step 1 of “Recording a Test,” on page 10.

2 Insert a call to the Sign_in action.

79


Choose Insert > Call to Existing Action. The Select Action dialog box opens.

Click the browse button next to the From test box. Select the ActionA test in
the Open Test dialog box, and click Open. Note that only reusable actions
from the ActionA test are displayed in the Select Action dialog box.
Select the Sign_in action. In the Location area, select At the end of the test.
Click OK. The call to Sign_in [ActionA] action is added to the end of the test
as a call to an external action with the icon.
Note that you cannot expand the Sign_in action call in the test flow in the
Keyword View. To view the steps in the Sign_in action, select it from the
Action List. The action call you inserted is read-only. To modify the action,
you must open the original (ActionA) test and modify the action there.
Select Test Flow in the Action List to return to the main flow of the test in
the Keyword View.

3 Insert a call to the ReturnHome action.
Use the instructions in step 2 to insert a call to the ReturnHome action from
ActionA. The ReturnHome action is added to the end of your test.

80


4 Save the test.
Select File > Save or click the Save button. Save the test as ActionB.

5 Modify the original ReturnHome action.
Choose File > Open. Browse to ActionA, and click Open.
Double-click the ReturnHome action icon to display its contents. (This is
equivalent to selecting the ReturnHome action from the Action List.)
Make sure that the Comment column is displayed in the Keyword View. If it
is not, right-click on the Keyword View column header and select Comment
from the displayed list.
In the Keyword View, select the ReturnHome action icon and choose
Insert > Step > Comment to add a comment about the purpose of the Home
step. The Insert Comment dialog box opens.

In the edit box, enter: Return to page used in first step of the test. Click OK.
The comment step is added as the first step in the action, and you can see
the comment text in the Comment column of that step. If the comment is
too long to see, it is displayed in a tooltip when you move your cursor over
the Comment column.

6 Save the test.

81


7 Confirm that the modification made in the original ReturnHome action
is also included in the calling test.
Choose File > Open. Browse to ActionB and click Open.
Double-click the ReturnHome [ActionA] action icon to display it. Note that
the comment you added to the original action (ActionA) also exists in the
calling test (ActionB).
In the Action toolbar, select Test Flow from the Action List to return to the
main flow of the test in the Keyword View.

Inserting a Copy of an Action
Now, you will insert a copy of the FlightOrder action.

1 Open the ActionB test.
Choose File > Open. Browse to ActionB and click Open.

2 Insert a copy of the FlightOrder action.
Choose Insert > Call to Copy of Action. The Select Action dialog box opens.

82


Click the browse button next to the From test box. Select the ActionA test in
the Open Test dialog box, and click Open. The actions from the ActionA test
are displayed in the Action List. Note that the description of the highlighted
action is displayed in the Action description box.
Select the FlightOrder action. In the Location area, select At the end of the
test. Click OK. The Copy of FlightOrder action is added to the end of the
test. Note that the call to the copy of the action you inserted is just like any
other action call in your test. You can modify the steps in the call to the
copied action just as you would those of any other action call.

3 Modify the Copy of FlightOrder action.
In the Keyword View, expand (+) Copy of FlightOrder > Welcome: Mercury
Tours > Find a Flight: Mercury. Select fromPort and click the Value cell.
Change the value in the Value cell to London and click any other row in the
Keyword View.

4 Call the Copy of FlightOrder action after the Sign_in action.
You want the Copy of FlightOrder action to be immediately after the Sign_in
action. Since you cannot drag any action to be immediately after a reusable
action (because it is read-only in the calling test), you must perform the
following steps to change the order of the action calls.
Select the Copy of FlightOrder action and drag it immediately below the
Action1 action in the Keyword View. Then, select the Sign_in action and
drag it immediately below the Action1 action in the Keyword View. The
Copy of FlightOrder action is now immediately after the Sign_in action.

5 Delete Action1 from the test.
Every new test contains a default Action1 action call. You can now delete the
Action1 action call.
In the Keyword View, select Action1 and choose Edit > Delete or press the
Delete key on your keyboard. A confirmation message opens. Click Yes to
delete the action call.

6 Save the test.

83


7 Confirm that the original FlightOrder action was not modified.
Choose File > Open. Browse to ActionA, and click Open.
Expand FlightOrder > Welcome: Mercury Tours > Find a Flight: Mercury.
Note that the change of departure city you made in the ActionB test did not
affect the original action in ActionA (New York is still the departure city in
ActionA).

Parameterizing an Action
If you look at the Data Table at the bottom of the QuickTest window in the
ActionB test, you will see four tabs: Global, Copy of FlightOrder,
Sign_in [ActionA], and ReturnHome [ActionA].

Note: If the Data Table is not displayed, choose View > Data Table to display
it.

The Global tab is a data sheet whose data is used for the entire test. If five
rows of data are displayed in the Global table, the test will run five times. In
addition, you can create data sets for each action, using the relevant action
sheet. If you parameterize a step using an action parameter and enter five
rows of data in the corresponding sheet, then that action will run five times
within each test iteration.

Note: The Sign_in [ActionA] and ReturnHome [ActionA] data sheets are
displayed in gray and cannot be edited because each of these data sheets
belong to the corresponding called action and can be edited from only the
called action’s original test.

84


In this section, you will create a data set for the FlightOrder action to check
how the application handles multiple orders during a single user session.

1 Open the ActionB test.
If the ActionB test is not already open, choose File > Open and browse to
ActionB. Click Open.

2 Select a step to parameterize.
Expand (+) Copy of FlightOrder > Welcome: Mercury Tours > Find a Flight:
Mercury.
In the toPort row in the Keyword View, click in the Value cell and then click
the parameterization icon . The Value Configuration Options dialog box
opens.

Enter the parameter information.
Select Parameter and confirm that the DataTable option is selected.
In the Name box, type ArrivalCity.

85


You are creating this data set exclusively for the Copy of FlightOrder action.
Therefore, select Current action sheet (local). Click OK to close the Value
Configuration Options dialog box.
QuickTest automatically adds the ArrivalCity column to the Copy of
FlightOrder data sheet and inserts San Francisco into the first cell of the
ArrivalCity column.

3 Parameterize additional steps.
It is not logical for a single customer to fly to two different locations on the
same dates, so it makes sense to parameterize the departure and arrival
dates.
In the Keyword View, select fromMonth. Use the procedures in step 2 to
parameterize the departure date. Make sure to select Current action sheet
(local) in the Value Configuration Options dialog box.
In the Keyword View, select toMonth. Use the explanations in step 2 to
parameterize the arrival date. Make sure to select Current action sheet
(local) in the Value Configuration Options dialog box.

4 Enter the parameterization data in the Data Table.
In the Data Table, click the Copy of FlightOrder tab.
Type Portland in the second row of the ArrivalCity column. Press Enter.
Type Oct in the second row of the departure and arrival date columns.

5 Set the action to run all the data in the local Data Table.
By default, QuickTest only runs one iteration of each action in a test. You
want QuickTest to use all the data in the Copy of FlightOrder tab.

86


Right-click the Copy of FlightOrder action in the Keyword View and choose
Action Call Properties. The Action Call Properties dialog box opens.

Select Run on all rows in the Run tab. If a message box opens, read it and
then click OK to close it. Click OK to close the Action Call Properties dialog
box.

6 Save the test.

You have now created a test that signs-in to the Mercury Tours site, submits
two flight orders: a flight from London to San Francisco from Dec 29 to
Dec 31, and a flight from London to Portland from Oct 29 to Oct 31, and
then logs out of the system by clicking the Home link.

87


Running and Analyzing a Multi-action Test
You will now run the ActionB test. The entire test will run only once, but the
FlightOrder action will run twice; one time for each set of data in the Copy
of FlightOrder data sheet.

1 Run the ActionB test.
Confirm that all Web browsers are closed.
Click Run or choose Test > Run. The Run dialog box opens.

2 Examine the test results.
Examine the Results Summary. The test is marked as Done. This indicates
that the test ran without any failures (there were no checkpoints to “pass”).

88


Expand Test ActionB Summary > ActionB Iteration 1 (Row 1) in the Test
Results window. Select the Copy of FlightOrder Summary action in the
results tree. Note that within the summary, the results of both iterations are
displayed.


89


90

9
Where Do You Go from Here?

Now that you have completed the exercises in this tutorial, you are ready to
apply the QuickTest concepts and the skills you learned to testing your own
application.


➤ Testing Your Own Application—Getting Started
➤ Getting Additional Information
➤ Documentation Updates

Testing Your Own Application—Getting Started
In this tutorial, you learned about the basic tools needed for testing
applications and Web sites.

We suggest that you follow the procedure outlined below when testing your
own application.

1 Plan your test.
Decide how to organize your test. Consider what users will want to
accomplish when deciding which operations to record. Confirm that your
application and QuickTest are set to match the needs of your test.

91

Lesson 9 • Where Do You Go from Here?

Decide which object repository mode to use for your test. The object
repository mode you choose determines the way that QuickTest stores
information about your application when you record tests. You can have a
separate action repository for each action and store the objects for each
action in its corresponding action repository, or you can store all the objects
in your test in a common (shared) object repository file. You can also use the
same shared object repository file for multiple tests.
If you are new to testing, you may want to use the object repository
per-action mode, as you can use this mode without making any other
changes to your test.
If you are familiar with testing, it is probably most efficient to work in the
shared object repository mode. In this mode, you can use one object
repository file for multiple tests. This means that object information that
applies to many tests is kept in one central location. When the objects in
your application change, you can update them in one location for all of
your tests.
For more information on choosing an object repository mode, refer to the

2 Record your test.
While recording (described in “Recording Tests” on page 9), follow the steps
you expect users to perform as they navigate within your application or Web
site.

3 Enhance your recorded test.
➤ Add checkpoints (described in “Creating Checkpoints” on page 25) to
search for specific values of a page, object, text string, or table.
➤ Replace fixed values in your test with parameters (described in
“Parameterizing Tests” on page 45) to check how your application
performs the same operations with multiple sets of data.
➤ Create output values (described in “Creating Output Values” on page 55)
to retrieve data during a test run.
➤ Where applicable, use regular expressions (described in “Using Regular
Expressions” on page 63) to increase the flexibility and adaptability of
your tests.

92


You can further enhance your test with programming and conditional and
loop statements, which add logic to your test. These are described in the

4 Debug your test.
Debug your test to check that it operates smoothly and without
interruption. For additional information about debugging, refer to the

5 Run your test.
Run your test on your application or Web site (described in “Running and
Analyzing Tests” on page 19) to check that the application functions as
expected.

6 Analyze the test results.
Examine the results of your test to pinpoint defects in your application.
(Refer to the appropriate sections of this tutorial to understand what to look
for in the test results.)

7 Report defects.
If you have Quality Center installed, you can submit any defects discovered
to a Quality Center database. (Quality Center is Mercury Interactive’s tool
for software test management. For additional information, refer to the
QuickTest Professional User’s Guide and the documentation included with
Quality Center.)

93


Getting Additional Information
For more information about QuickTest Professional, refer to the printed
documentation and online resources provided with QuickTest Professional.

Printed Documentation
In addition to this tutorial, QuickTest Professional comes with the following
printed documentation:

➤ QuickTest Professional Installation Guide
Explains how to install QuickTest Professional.

➤ QuickTest Professional User’s Guide
Provides step-by-step instructions for using QuickTest Professional to test
your application or Web site. The User’s Guide describes many useful testing
tasks and options not covered in this tutorial.

➤ QuickTest Professional Shortcut Key Reference Card
Lists commands that you can execute using shortcut keys.

Online Resources
In addition to this tutorial, the following online documentation is included
with QuickTest Professional:

➤ Readme (available from the QuickTest Professional Start menu program
folder)
Provides the latest news and information about QuickTest Professional.

➤ What’s New in QuickTest Professional (available from Help > What’s New in
QuickTest)
Describes the newest features, enhancements, and supported environments
in the current version of QuickTest Professional.

94


➤ Printer-Friendly Documentation
Displays the complete documentation set in Adobe portable document
format (PDF). Online books can be read and printed using Adobe Reader,
which can be downloaded from the Adobe Web site (http://www.adobe.com).

➤ QuickTest Professional Context-Sensitive Help (available from dialog boxes
and windows)
Describes specific QuickTest dialog boxes and windows.

➤ QuickTest Professional Tutorial (available from the QuickTest Professional
Welcome window, the Help menu, and the QuickTest Professional Start
menu program folder)
Teaches you basic QuickTest skills and shows you how to start designing
tests for your applications.

➤ QuickTest Professional User’s Guide (available from Help > QuickTest
Professional Help)
Provides step-by-step instructions for using QuickTest Professional to test
your application or Web site. The User’s Guide describes many useful testing
tasks and options not covered in this tutorial.

➤ QuickTest Professional Object Model Reference (available from Help >
QuickTest Professional Help)
Describes QuickTest Professional test objects, lists the methods and
properties associated with each object, and provides syntax information and
examples for the methods.

➤ QuickTest Professional Automation Object Model Reference (available from
the QuickTest Professional Start menu program folder and from Help >
QuickTest Automation Object Model Reference)
Provides syntax, descriptive information, and examples for automation
objects, methods, and properties. It also contains a detailed overview to help
you get started writing QuickTest automation scripts. The automation object
model assists you in automating test management, by providing objects,
methods and properties that enable you to control virtually every QuickTest
feature and capability.

95


➤ VBScript Reference (available from Help > QuickTest Professional Help)
Contains Microsoft VBScript documentation, including VBScript, Script
Runtime, and Windows Script Host.

➤ Mercury Tours sample Web site and the Mercury Tours Windows sample
flight application (both available from the QuickTest Professional Start
menu program folder)
The sample applications for QuickTest Professional are the basis for many of
the examples in the documentation. The examples and instructions in this
tutorial are based on the Mercury Tours Web site
(http://newtours.mercuryinteractive.com).

➤ Customer Support Online (available from Help > Customer Support Online)
Uses your default Web browser to open the Mercury Customer Support Web
site. This site enables you to browse the knowledge base and add your own
articles, post to and search user discussion forums, submit support requests,
download patches and updated documentation, and more. The URL for this
Web site is http://support.mercury.com.

➤ Send Feedback (available from Help > Send Feedback)
Enables you to send online feedback about QuickTest Professional to the
product team.

➤ Mercury Interactive on the Web (available from Help > Mercury Interactive
on the Web)
Opens Mercury Interactive’s home page in your default Web browser. This
site provides you with the latest information about Mercury Interactive and
its products, including new software releases, seminars and trade shows,
customer support, and educational services. The URL for this Web site is
http://www.mercury.com.

96


Documentation Updates
Mercury Interactive is continuously updating its product documentation
with new information. You can download the latest version of this
document from the Customer Support Web site (http://support.mercury.com).

To download updated documentation:
1 In the Customer Support Web site, click the Documentation link.
2 Under Select Product Name, select QuickTest Professional.
Note that if QuickTest Professional does not appear in the list, you must add
it to your customer profile. Click My Account to update your profile.
3 Click Retrieve. The Documentation page opens and lists the documentation
available for the current release and for previous releases. If a document was
recently updated, Updated appears next to the document name.
4 Click a document link to download the documentation.

97


98

Index
A checkpoints (continued)
table 35
Action List 6
text 33
Action Properties dialog box 87
copying actions 82
Action toolbar 6
creating actions 70
actions 69–89
creating checkpoints 25–43
analyzing test results 88
creating tests
calling 79
procedure 91–93
copying 82
with multiple actions 69–89
creating 70
with output values 55
inserting existing 79
customer support, online 96
parameterizing 84
running tests 88
splitting 73 D
Active Screen button 5 Data Table 6
analyzing test results 21–24 assigning parameter values 48
actions 88 Data Table button 5
checkpoints 38 Debug toolbar 5
output values 61 Debug Viewer button 5
parameterized tests 51 Display selected action button 6
regular expressions 67 documentation updates 97
automated testing, benefits 1 documentation, online 94–96
documentation, printed 94
B
Back button 6 E
End Transaction button 5
C
calling actions 79 F
Checkpoint Properties dialog box 29, 36 File toolbar 5
checkpoints
analyzing test results 38
creating 25–43 H
page 31 Help, online 95
running tests with 38
standard 27, 41

99

Index

I parameterized tests
modifying 49
input parameters 45–53
running and analyzing results 51
Insert Checkpoint button 5
parameterizing
Installation Guide 94
actions 84
tests 45–53
K parameters
Keyword View 15 definition 45
input 45–53
Print button 5
L
Low-Level Recording button 5 Q
Quality Center Connection button 5
M QuickTest
manual testing, drawbacks 1 window
menu bar, QuickTest window 5 Data Table 6
Mercury Interactive on the Web 96 status bar 6
Mercury Tours sample application 7, 96 title bar 6
Microsoft VBScript Reference 96 QuickTest resources, printed and online
modifying parameterized tests 49 94–96
multiple actions 69–89 QuickTest window 4
Action toolbar 6
N Debug toolbar 5
File toolbar 5
New Action button 5 menu bar 5
New button 5 Testing toolbar 5
title bar 5
O
Object Repository button 5 R
Object Selection - Checkpoint Properties Readme, QuickTest Professional 94
dialog box 28, 31, 35 Record and Run Settings dialog box 11
Object Spy button 5 Record button 5
online resources 94–96 recording tests 9–17
Open button 5 regular expressions 63–68
Options button 5 resources, QuickTest, printed and online
output values 55–62 94–96
Run button 5
P Run dialog box 20
running tests 19–24
Page Checkpoint Properties dialog box 32
parameterized tests 51
page checkpoints
with actions 88
creating 31
with checkpoints 38
results 39
with output values 61
parameter values, in Data Table 48
with regular expressions 67

100

Index

S toolbars (continued)
File 5
sample application, Mercury Tours 7, 96
Testing 5
Save button 5
Tutorial, QuickTest Professional 95
Split Action button 5
typographical conventions vii
Split Action dialog box 73
standard checkpoints
creating 27 U
results 41 updates, documentation 97
Start Transaction button 5 User’s Guide 94, 95
status bar, QuickTest window 6
Stop button 5
support, online 96 V
values, output 55–62
T
table checkpoints W
creating 35 Web site, Mercury Interactive 96
results 40 What’s New in QuickTest Professional 94
technical support. See customer support
test results
actions 88
analyzing 21–24
checkpoints 38
output values 61
regular expressions 67
Test Results button 5
Test Results window 21
Test Settings button 5
testing applications, how to begin 91–93
testing process 2
Testing toolbar 5
tests
analyzing results 21–24
procedure for creating 91–93
recording 9–17
running 19–24
Text Checkpoint Properties dialog box 34
text checkpoints
creating 33
results 42
Text Output Value Properties dialog box 57
title bar, QuickTest window 5, 6
toolbars
Action 6
Debug 5

101

Qtp Tutorial

More Related Content

What's hot (13)

Viewers also liked (20)

Similar to Qtp Tutorial (20)

Qtp Tutorial