DAY1 Updated

United States | Australia | Canada | India | United Kingdom keane.
com
QTP Training Program
©2006 Keane, Inc. All rights reserved. Confidentiality: The concepts and methodologies contained herein are proprietary to Keane, Inc.
Duplication, reproduction or disclosure of information in this document without the expressed written permission of Keane is prohibited. Keane Testing Services 1
United States | Australia | Canada | India | United Kingdom keane.com
Course Objectives
On completion of the course the participant should be able
to do the following:
• Installation , Licensing and Add-Ins Issues of QTP
• Generation and Running of Test Scripts
• Parameterize tests
• Checkpoints
• Reporting & Analysis of results
Software Required: QTP 8.0 and TD

Duration of the course: 5 days
Target Audience
• Candidates with Knowledge of the Testing Process
• Candidates with Knowledge of any object oriented

Programming language
Day 1 Schedule
Day Session Duration (Hrs) Topic
1 S1 2 •Test Automation Process Overview
•Benefits of Automation
•Commonly Used Tools
•Installation of QTP and License Issues
•Add-Ins
•Framework Criteria
•Lab
S2 4 •Working with QTP
•Creation of Scripts (Recording an Application)
•Record and Run Settings
•Recording Types
•QTP Standard Views
•Active Screen Capture Level Settings
•Introduction to Object Repository
•Actions
•Transaction Response Time
•LAB
S3 2 •Data Driven Tests
–Data Tables
–Parameterization
•LAB
Day 2 Schedule
Day Session Duration Topic
(Hrs)
2 S1 2 •Checkpoints
–Types of Checkpoints
–Output Values
•LAB
S2 2 •Regular Expressions
•Virtual Objects
•Synchronization
•LAB
S3 2 •Recovery Management
•LAB
S4 2 •Variables
–Action Parameters
–Test Parameters
–Environment Variables
•Step Generator
•LAB
Day 3 Schedule
Day Session Duration Topic
3 S1 2 •Test Automation Process overview
•Design Considerations
–Object Repository Settings
•Optional Step
•Execute Script
•LAB
S2 2 •Executing QTP Script with TD

•LAB
S3 2 •Analysis of Results
– Test Results
•Reporting
– Types of Reporting
– Reporting Functions
•LAB
S4 2 •QTP Test Settings

•QTP Options Settings
•Reusability Library
•QTP Vs Other Automation Tools
•LAB
DAY 1
Session 1
Test Automation Process Overview

Plan
Automation Analyse Results
Test Lead and Log Defects
Framework
Create
Test Data Analyst
Test Data for
Automation
Test Engineer Generate\Obtain Generate Review Execute

Test Cases Scripts Scripts Scripts
Generate\Obtain Test Cases and Test Data Creation
Benefits of Automation
• Repeatable, Reliable & Scalable
• High Consistency
• High Traceability
• A screen in a business scenario can be tested with a large
volume of test data in a short interval
• Reports are generated automatically after execution of an
automated script
• Automated scripts can be planned & scheduled from Test
Management tool like TestDirector
• Team size can be limited once the manual test scripts are
automated for every new version Testing
• Human errors are minimized
• No reliance on ‘business expertise’ in order to execute
automated test script
Commonly Used Functional Test Automation Tools
• Mercury - WinRunner
• Mercury - QTP
• IBM Rational – Rational Robot
• Compuware - QARun
Quick Test Professional
QTP
• Vendor: Mercury Interactive
• Scripting Language: VBScript
• Support Site: www.mercury.com
• Latest Version: QTP 8.2
• Current Reference Version for slides: QTP 8.0
System Requirements for Installation of QTP

Mercury: IBM-PC or compatible with a Pentium II 266 MHz microprocessor (366 MHz
Computer/
recommended)
Processor: TBL Recommends: IBM-PC or compatible with a Pentium IV 1GHz microprocessor
Operating Windows 2000-Service Pack 3 or Service Pack 4, Windows XP-Service Pack 1, or Windows 2003
System: Server.
Mercury :128 MB of RAM (256 MB recommended)
Memory: TBL Recommends: 512MB of RAM
Mercury :250 MB of free disk space for application files and folders, and an additional 120 MB
of free disk space on the system disk (the disk on which the operating system is installed).
Free Hard After QTP is installed, it is recommended to have at least 150 MB free disk space on the system
Disk Space: disk for the operating system and QTP to run correctly.
TBL Recommends: 1GB of Hard disk space
Browser: Microsoft Internet Explorer 5.5 Service Pack 2 to 6.0 and above
QTP Licensing
• Types of Licenses
– Demo
– Seat
– Concurrent
• License Keys
– Main license key
– Add-in license key
QTP Add-ins
• Default Add-ins
– Active X Controls
– Web Add-in
– Visual Basic Manager
• Additional Add-ins
– Java add-in
– Oracle add-in
– Siebel add-in
– SAP add-in
– Terminal Emulator add-in
– .Net add-in
– PeopleSoft add-in
How to choose an Add-in
• Does the application to be tested contain any

objects apart from standard MFC objects or web
Controls?
• Does the web application contain any java applets,
java tables or sliders?
• Does the web page have an extension of .aspx ?
SAP Patch

Plan
Automation Analyze Results
Framework
Create
Test Data Analyst
Test Data for
Automation
Test Engineer Generate Generate Review Execute

Design Considerations
• Understand the Customer’s Environment

• Manual Test Scripts and Scenarios must be
reviewed for
– Process Flow
– Check Points
– Availability of Functional Consultant
• Test Data
• Application access to Offshore
• Acceptance Criteria
Framework Criteria
• Reusability
– Library functions
– Scripts
– Actions
• DataDriven Tests
• Naming Conventions
– Script Name: <Scenario ID>
– Test data file name: <Scenario ID.xls>
– Action Name: <Transaction Name>
Folder Structure
The suggested folder structure

• QTP_SCRIPTS
• QTP_RESULTS
• QTP_TESTDATA
• QTP_FUNCTIONS
• QTP_SCENARIOS
• An Environment Variable is used to map the path to Test

Data File:-
– E.g. instead of \\TestingLab\QTP_TESTDATA\S007_015.xls
– Create an environment variable “Drive” in settings, set it to the path
– In Script: Environment(“Drive”) + “QTP_TESTDATA\S007_015.xls”
Script Generation Considerations
• Easy input of test data

– Take input from an External source like Excel sheets
– Write output back into the External Source
– Record completion status of each iteration
– Iterate the run ‘n’ number of times
• Flexibility in Test Run
– Ensure that the scripts run independently
– Ensure that the scripts run sequentially
• Easy Maintenance
– Using Shared Objects
– Ensure reusability
– Follow standards
– Peer Review
LAB 1.1
• Explore various Licensing Options

• Explore Add-ins
End of Session 1
Session 2

Plan
Automation Analysing Results
Framework
Create
Test Data Analyst
Test Data for
Automation

Working With QTP
Working with QTP

• Working with QTP involves various phases
– Recording an Application to generate a script
– Enhancing the Script with necessary CheckPoints
– Execution of Scripts
– Analysis of Results
– Reporting Bugs
Recording an Application
• Select File New Test

• Click on the ‘Record’
button
• Perform actions on the
application
• Click ‘Stop’ at the end
of Recording session
Record and Run Settings
• Pops automatically while

recording a new Test
• Enables to set the details
of which application to
record
• If any other add-in(s) are
loaded,the corresponding
tabs are displayed
additional to existing
ones
Recording Modes
There are 3 recording modes available

• Standard Recording: Typically used for normal
recording to capture operations on the application
• Analog Recording: Generally used for Bitmap

Capturing
• Low level Recording: Captures the mouse

movements with respect to the co-ordinates on the
Application Window.
QTP Standard Views
Enable clear understanding of various representations of

a Test Script
– Expert View: VBScript statements for actions
– Keyword View: Hierarchical Representation of

actions
– Active Screen View: Pictorial view of the

currently active Screen
QTP Standard Window
Expert View
Data Sheets
Active Screen View

QTP Standard Window
Keyword View
Expert View
• Displays each operation performed on the

application in the form of VBScript statements
• The view is a Script Editor with various script
editing capabilities
• For each object and method in an Expert View
statement, a corresponding row exists in the
Keyword View and a corresponding Active Screen
in the Active Screen view, which enables easy
traceability
Keyword view
• Hierarchal representation of ‘Actions’ and the

operations within the Actions contained in a Script
• Contains various columns like Items, Operation,
Value and Documentation which provide detailed
description of each object
Active Screen view
• Provides pictorial view of the currently Active

Screen
• The Current Active Screen is depicted depending
on the statement selected in the Expert view
• Enables easy adding of Checkpoints, Sync Points
and adding objects to Object repository
Object Repository
Introduction to Object Repository
• QTP stores information it learns about a window

or an object in the ‘Object Repository’
• Windows and Objects are stored in a hierarchal

fashion
• Each Object is qualified with certain properties

and methods ,which can be modified here
Object Repository
Object Hierarchy
Objects
• Objects are GUI entities, qualified with some

properties, data and the methods necessary to
operate on that data
• Property describes the object defined, which
differentiates the given object with other objects
• Methods are functions, required in order to
manipulate the object properties
• Example: A Button is said to be an object which
consists of properties such as ‘Enabled’, ‘Size’ and
methods such as ‘onClick’, ‘OnFocus’ etc
How QTP stores Objects
Object
Add objects Repository
Generates Script
using object
identification
settings
QTP
TEST SCRIPT
Class Hierarchy
“Dialog” Object
Child Object for Method for

“Dialog” Object “WinEdit”
Object
Parent Object named
Dialog as “Login”
Child Object
WinEdit named as “Agent
Name:”
“Set” is the method associated with “WinEdit” object
Active Screen Settings

• Tools>Options>Active
Screen
• The selection of the
appropriate Active Screen
Capture level influences
the storage space properties
captured and the view of
the Active screen
• Complete
• Partial
• Minimal
• None
Active Screen Capture Levels
• Complete: Captures ALL Objects in the Active

Screen of each step. i.e. even if the object is not
used while performing the action , any object on
the Screen can be added to the repository. Also
Dynamic Changes on Web pages are saved
• Partial: Same as the complete mode, but this

mode captures only properties related to the
recorded objects in other steps under the same
parent object
Contd…
Active Screen Capture Levels
• Minimal: Captures only minimal set of properties

in each object. This doesn’t allow addition of
unrecorded objects from the Active Screen to the
repository at a later stage
• None: Doesn’t Capture the Active Screen for any

Action
Actions
Actions
• Actions divide a Test into logical units,i.e specific set

of activities that are performed in the application
• A Test becomes Modular and Efficient by inserting calls
to multiple actions in the Test Script
• The Keyword view depicts the hierarchy of Actions in
the Script
Window depicting Actions in a Test
Actions in a
Test
Keyword view depicting Action Hierarchy
Exit Action Login Action
Types of Actions
• There are three types of actions:

– Reusable Action - An action
that can be called from any test
– External Action - A reusable
action stored with another test.
External actions are read-only in
the calling test. They can be
modified only in the test with
which they are stored
– Non-Reusable Action - An
action that can be called only in
the test with which it is stored,
and can be called only once
Action Template
• An Action Template is useful when one or more

common statements are to be included in every
new action of the Test
• For example, if the Script Author name is to be
mentioned for all the actions, the following lines
can be added to the action template
To create an Action Template
• Create a text file containing the comments, function

calls, and other statements that are to be included in
the action template.
• The text file must be in the structure and format used
in the Expert View
• Save the text file as ActionTemplate.mst in the
<Quick Test Installation Folder>\dat folder
Transaction Response time
• Transaction Response Time is used to measure the

response time of any transaction
– Can be done for a single transaction
– Can be done for multiple transactions
• Results are logged in Test results log for every
iteration
• Response time measured from start to end of one
iteration (within login and logoff)
Transaction Response time
Transaction log
LAB 1.2
• Record Scripts for a Web and a Windows

application
• Generate Scripts in various recording modes
• Record a Script and split it into various Actions
• Create different types of Actions
End of Session 2
Session 3
Plan
Test Lead Automation Analyze Results
Framework and Log Defects
Create
Test Data Analyst Test Data for
Automation
Generate\Obtain Generate Review Execute

Test Engineer
Data Driven Tests
Data Driven Tests
• When an application is tested, the major goal is to

check how it performs same operations with
multiple sets of data
• Data Driven Tests provide solution for this
Data Driven Tests
There are two types of data sheets in QTP

• Globalsheet
• Localsheet
Globalsheet
• Values stored in Globalsheet are accessible in all

the actions of a Test
• Globalsheet is unique for a Test
• For storing a value in the global sheet the
following function is used:
Datatable.Value(“Fieldname”,”Global”) = Value
• For retrieving values from the global sheet the
Value = Datatable.Value(“Fieldname”,”Global”)
Localsheet
• Every Action in a script has a corresponding

Localsheet
• Name of the Localsheet for a particular action is
same as the action name
• For using the data from the Local sheet the
– Datatable.Value(“Fieldname”,dtlocalsheet)
or
– Datatable.Value(“Fieldname”,”Sheetname”)
Organization of Data sheets for a test

• Organization of Global and Local sheets
corresponding to the actions used in the script are
shown below
Action
name:
“Login”
Local Sheet for

“Login” Action
Global
Sheet
Parameterization using Data driven Wizard
• The Data Driver enables easy parameterization of any number of

property values for test objects
• Steps for parameterization using Data driven Wizard:

– Go to Tools  select Data Driver option
– A list of all the properties of all the objects which can be
parameterized is displayed
– Select a value for parameterization
Contd…
• Select the parameterization method:

– Step-by-step parameterization
– parameterize all
Contd…
Keane Testing Services 68
Duplication, reproduction or disclosure of information in this document without the expressed written permission of Keane is prohibited.
• Step-by-step Parameterization
– Enables to view the current values of each step containing
the selected value
– There is a choice to choose the step to parameterize , also
the value to parameterize
Contd…
• Parameterize all
– Enables parameterization of all occurrences of the
selected value throughout the action
– When this option is selected, the ‘Parameter details’
area is enabled
Sample DataDriven Test
Importing and Exporting Datasheets
• Importing and Exporting of Datasheets is a feature

of QTP which enables effective reading, writing and
manipulating the data in an excel sheet
Importing a Datasheet
• Imports a sheet of a specified file to a specified

sheet in the run-time Data Table
• The data in the imported sheet replaces the data in
the destination sheet
• All the fields in the imported sheets should match
with the data used in the script
• There are two functions for Importing,
– Importing the whole excel file
– Importing the sheets in the file
Contd…
Importing Datasheet
• Syntax to import the whole excel file
– Import “filenamewithpath”
• Syntax to import the sheets in a file

– Importsheet
“filenamewithpath”,”sourcesheetname””destinationsheetname”
• Example: Source
Sheet Index
External Destinatio
DataSheet n Sheet
Index
Exporting Datasheet
• Exports a specified sheet of the run-time Data Table to the

specified file
– If the specified file does not exist, a new file is created and the
specified sheet is exported
– If the current file exists, but the file does not contain a sheet with
the specified sheet name, the sheet is inserted as the last sheet of
the file
– If the current file exists and the file contains the specified sheet,
the exported sheet overwrites the existing sheet
• There are two functions for Exporting
– Exporting the whole excel file
– Exporting the sheets in the file
Contd…
Exporting Datasheet
• Syntax to export the whole Excel file:
– Export “filenamewithpath”
• Syntax to export sheets from an Excel file:

– Exportsheet
“filenamewithpath”,”sourcesheetname”
• Example:
Destination Source
Filename Sheet Index
Column Naming Convention
• O_* - Output value- Anything that is written out

by QTP (All the rows under this column are left
blank at the start of run)
• C_* - Checkpoint Input – Value that’s taken to
compare a checkpoint (All the rows under this
column are to be filled at the start of run)
• No Prefix – Input value to QTP (All the rows
under this column are to be filled at the start of
run)
Sample Input Excel file
Nine rows of input data Output from QTP Completion Status

of every iteration
Instructions on how to fill the excel file
Each sheet corresponds to a transaction
Main functions of the DataTable object

• Importsheet : Used to Import a sheet into the script, to
access the entire contents of the sheet in the test
– Syntax:
Datatable.Importsheet(“nameofExcelfilewithpath”,
“nameofthesourcesheet”,“nameofthedestinationsheet”)
• Exportsheet : Used to Export a sheet from the script, all

the data including output values are stored in the default
sheet for the action, this sheet is exported and stored in a
specified location by this function
– Syntax:
Datatable.Exportsheet(“nameofExcelfilewithpath”,
“nameofthesheet”)
Contd…
Main functions of the DataTable object
• GetRowCount: Returns the number of rows in a particular

sheet
– Syntax:
Datatable.GetSheet(“Sheetname”).GetRowCount
• GetCurrentRow: Returns the current row number of a

particular sheet
– Syntax:
Datatable.GetSheet(“Sheetname”).GetCurrentRow

Plan
Automation Analysing Results
Framework
Create
Test Data Analyst
Test Data for
Automation

Reviewing Scripts
• Recorded Scripts are to be reviewed for

correctness and eliminate any recording errors
• Walk Throughs, Peer Reviews can be adopted
LAB 1.3
• Work on Parameterization using Global and

LocalSheets
• Work on Importing and Exporting DataSheets
Lab 1.3
End of Session 3
Recap
Recap
• Test Process Automation Overview

• Benefits of Automation
• QTP Licenses and Add-Ins
• Recording a Test on QTP
• QTP Views
• Object Repository
• Splitting Scripts into Actions
• Transaction Response Time
• Data Driven Tests
End of Day 1

DAY1 Updated

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

DAY1 Updated

Transféré par

Droits d'auteur :

Formats disponibles

United States | Australia | Canada | India | United Kingdom keane.

QTP Training Program

Software Required: QTP 8.0 and TD

• Candidates with Knowledge of any object oriented

S2 2 •Executing QTP Script with TD

S4 2 •QTP Test Settings

Test Automation Process Overview

Test Engineer Generate\Obtain Generate Review Execute

Generate\Obtain Test Cases and Test Data Creation

Commonly Used Functional Test Automation Tools

• IBM Rational – Rational Robot

Quick Test Professional

System Requirements for Installation of QTP

How to choose an Add-in

• Does the application to be tested contain any

Test Automation Process Overview

Test Engineer Generate Generate Review Execute

• Understand the Customer’s Environment

The suggested folder structure

• An Environment Variable is used to map the path to Test

Script Generation Considerations

• Easy input of test data

• Explore various Licensing Options

Test Automation Process Overview

Test Engineer Generate\Obtain Generate Review Execute

Working With QTP

Working with QTP

– Recording an Application to generate a script

– Enhancing the Script with necessary CheckPoints

• Select File New Test

Record and Run Settings

• Pops automatically while

There are 3 recording modes available

• Analog Recording: Generally used for Bitmap

• Low level Recording: Captures the mouse

QTP Standard Views

Enable clear understanding of various representations of

– Expert View: VBScript statements for actions

– Keyword View: Hierarchical Representation of

– Active Screen View: Pictorial view of the

QTP Standard Window

Active Screen View

QTP Standard Window

• Displays each operation performed on the

• Hierarchal representation of ‘Actions’ and the

Active Screen view

• Provides pictorial view of the currently Active

Introduction to Object Repository

• QTP stores information it learns about a window

• Windows and Objects are stored in a hierarchal

• Each Object is qualified with certain properties

• Objects are GUI entities, qualified with some

How QTP stores Objects

Child Object for Method for

“Set” is the method associated with “WinEdit” object

Active Screen Settings

Active Screen Capture Levels

• Complete: Captures ALL Objects in the Active

• Partial: Same as the complete mode, but this

Active Screen Capture Levels

• Minimal: Captures only minimal set of properties

• None: Doesn’t Capture the Active Screen for any