Qtp certification training_material

HP AIS Functional Testing V11
Training Material with Mock test

• Software Test Automation is the process of
automating the steps of manual test cases using
an automation tool Or utility to shorten the testing
life cycle with respect to time
• This process involves automation of a manual
process. Automation Testing is used to re-run the
test scenarios that were performed manually,
quickly and repeatedly.
• Apart from regression testing, Automation testing
is also used to test the application from load,
performance and stress point of view. It
increases the test coverage; improve accuracy,
saves time and money in comparison to manual
testing.
Introduction to Automation

Repeatable
You can test how the Web site or application reacts
after repeated execution of the same operations.
Reliable
Tests perform precisely the same operations
each time they are run, thereby eliminating
human error.
Also reduces the chances of missing out any
scenario.
Fast
Tests are run significantly faster than human
users.
Reusable
You can reuse tests on different versions of a
Web site or application, even if the AUT under
goes changes.
Programmable
You can program sophisticated tests that
bring out hidden information.
Automation
Reliable Fast
Advantages of Automation

• Regression Testing Cycles are long and iterative
• If the application is planned to have multiple releases / builds
• If it’s a long running application where in small enhancements/ Bug Fixes keeps
happening
• Test Repeatability is required
When Automation is applicable?

Tests that need to be run for every build of the application (sanity level)
Tests that use multiple data values for the same actions (data driven tests)
Tests that require detailed information from application internals (e.g. SQL, GUI
attributes)
Which test cases to automate ?

Usability testing – "How easy is the application to use?"
One-time testing, "ASAP" testing – "We need to test NOW!"
Ad hoc/random testing – based on intuition and knowledge of application
Tests without predictable results
Which test cases should not be automate ?

Automation Test execution Process
Test data
creation in
automation
format.1
Execute
automated
test script.2
Analyze test
result and
check for any
deviation
from standard
behavior
3 Report
issues if
any or
report
success
4

Web
SAP
Siebel
WPF
Oracle
Java
People
Soft
Delphi
.Net
Windows
Mobile
Flex
Silver
light
Web
Services
QTP Supported Technologies

Custom
•Java
•.NET
•Terminal Emulator
•PowerBuilder
Typical
•Web
•ActiveX
•Visual Basic
QTP Add-Ins

• Specific to the computer on which it is installed
Permanent Seat License
• It can be used by multiple Quick Test users
Network-based concurrent license
License
Network-based
concurrent
license
Permanent
seat license
QTP License

Quick Test
Window
Start page
Key word
View
Expert
View
Function
Library
Active
Screen
Information
Pane
Available
Keywords
and Test
Flow Pane
Resources
Pane
Missing
Resources
Pane
Process
Guidance
Pane
QTP Windows

View > Start Page
 What’s New
 Process guidance List
 Keyword Driven Testing
 Application Area
 Business Components
 Short cut links
 Recently opened test/Library files
Start Page

The Keyword View enables you to create and view
the steps of your test in a keyword-driven,
modular, table format
The Keyword View is comprised of a table-like
view, in which each step is a separate row in the
table, and each column represents different parts
of the steps
Each operation performed on the application
during a recording session is recorded as a row in
the Keyword View
For each row in the Keyword View, Quick Test
displays a corresponding line of script in the Expert
View
Keyword View

• A test object on which you perform a step
• You must select an option from the Item column before you can
add additional content to a step
Item
• The operation to be performed on the item
Operation
• The argument values for the selected operation
Value
• The Documentation cell is read-only
• This cell displays an explanation of what the step does in an easy-
to-understand sentence
Documentation
Keyword View Default Columns

Quick Test displays each operation performed on your application in the form of a script,
comprised of VBScript statements
For each object and method in an Expert View statement, a corresponding row exists in
the Keyword View
Expert View

View > Active Screen
The Active Screen provides a snapshot of your application as it appeared when you performed
certain operation during a recording session
The Active Screen contains detailed property information about each object displayed on the page
Active Screen

View > Information Pane
The Information pane provides a list of syntax errors in your test or function library scripts.
When you switch from the Expert View to the Keyword View, Quick Test automatically checks for syntax errors
in your script, and shows them in the Information pane
If the Information pane is not currently displayed, Quick Test automatically opens it when a syntax error is
detected
Information Pane

View > Available Keywords Pane
The Available Keywords pane enables you to drag and drop objects or calls to functions into your
component. When you drag and drop an object into your component, Quick Test inserts a step
with the default operation for that object
Available Keywords Pane

View > Test Flow
Test Flow pane comprises of hierarchy of
actions and action calls in the current test, and
shows the order in which they are run
Each action is displayed as a node in a tree,
and includes calls to all of a test's actions.
The steps of the action that you double-click in
the Test Flow pane are displayed in the
Keyword View and Expert View.
Test Flow

View > Resources
Components are associated with resources such as
function libraries, recovery scenarios, and object
repositories (via an application area)
Quick Test displays all the resources associated with
a component in the Resources pane. The Resources
pane enables you to view and open all of the
resources in your component
Resources Pane

View > Missing Resources
The Missing Resources pane provides a list of
the resources that are specified in your test
but cannot be found
Missing resources can include missing
function libraries, missing recovery scenarios,
a missing XML file, unmapped shared object
repositories, and parameters connected to
shared object repositories
Each time you open function library, Quick
Test automatically checks if all specified
resources are accessible. If not, Lists them in
the Missing Resources pane
If the Missing Resources pane is not opened,
Quick Test automatically opens it when a
missing resource is detected
Missing Resources Pane

Issues
 Multiple matching objects found in AUT
 No matching objects found in AUT
Object Recognition Problems
Causes
 Change in Runtime Objects in AUT
 Insufficient Regular expressions used
Solutions
 Update Test Object’s properties
 Use Regular Expressions
 Use Virtual Objects
 Use Recovery Scenarios
 Use Descriptive Programming

Introduction to Virtual Object
Your application may contain objects that behave like standard objects but
are not recognized by UFT. You can define these objects as virtual objects
and map them to standard classes, such as a button or a check box.
 QTP doesn't support virtual objects for analog or low-level recording.
 Checkpoints cannot be added on Virtual Objects.
 Virtual Object is NOT controlled by Object Repository.
 Though we map an object to a particular class (button or List), all the
methods of the native objects are not supported by Virtual objects.
 Object Spy cannot be used on Virtual Object.
 The test execution will fail if the screen resolution changes as the co-
ordinates change.
 Application Window should be of same screen size so that Virtual objects
are captured correctly.

Introduction to Shared OR
• SOR contains information that enables UFT to identify the objects in your
application.
• UFT enables you to maintain the reusability of your tests or components by
storing all the information regarding your test objects in shared object
repositories.
• You use the Object Repository Manager to create and maintain shared object
repositories.
• You can work with shared object repositories saved both in the file system and
in an ALM project.
• When objects in your application change, the Object Repository Manager
provides a single, central location in which you can update test object
information for multiple tests or components.
• Extension of SOR is .tsr

Local OR Vs Shared OR
Local Object Repository(LOR) Shared Object Repository (SOR)
This Object Repository is available one for each
action.
This type of OR is available for multiple tests and for
multiple actions.
This is the OR that is available for each tests by
default.
This type of OR is usually used in frameworks
considering reusability and maintainability.
Local Object Repository is Editable in Object
Repository.
Shared Object Repository is read only by default but
can be edited in Object Repository Manager.
It is NOT a standalone file that can edited. SOR is a standalone file that can be edited easily.
It is Saved with an Extension .bdb SOR is saved with an extension .tsr
It Should be used when not many tests are working
on the same screens of the application under test.
SOR Should be used when there are different
scripts interacting with the same type of the object.

How to create Shared OR
1. Exporting Local OR to shared OR
2. Resource -> Object repository (Ctrl +
R)
• Object Repo- > File -> Export Local
Object
1. Creating Shared OR using object
repository manager (ORM)
2. ORM -> File -> New
3. Add object

Importing and Exporting Shared OR Using XML
• You can import and export shared object repositories from and to XML files.
• To export to XML:
• In the Object Repository Manager, select File > Export to XML. The Save
XML File dialog box opens.
• UFT exports the objects in the shared object repository to the specified
XML file, and a summary message box opens showing information
regarding the number of test objects, checkpoint and output objects,
parameters, and metadata that were successfully exported to the specified
file.
• To import from XML:
• In the Object Repository Manager, select File > Import from XML. The
Open XML File dialog box opens.
• The XML file is imported and a summary message box opens showing
information regarding the number of test objects, checkpoint and output
objects, parameters, and metadata that were successfully imported from
the specified file.

Comparing Shared object Repositories
• The Object Repository Comparison Tool enables you to compare two
shared object repositories, and view the differences in their objects, such
as different object names, different test object descriptions, and so on. The
tool is accessible from the Object Repository Manager.
• After the comparison process, the Comparison Tool provides a graphic
presentation of the objects in the object repositories, which are shown as
nodes in a hierarchy.
• Objects that have differences, as well as unique objects that are included
in one object repository only, can be identified according to a color
configuration that you can specify.
• Objects that are included in one object repository only are indicated in the
other object repository by the text "Does not exist".
• You can also view the properties and values of each object that you select
in either object repository.

Object Repository Comparison Tool
Navigation
Step 1: Navigate to "Resources" >> "Object Repository Manager"
Step 2: Goto "Tools" >> "Object Repository Comparison Tool“

Object Repository Comparison Tool (Contd..)

Object Repository Comparison Tool –
Comparison statistics

Filter Settings
This dialog box enables you to filter objects in the repository panes of the
Object Repository Comparison Tool Main Window.

Color Settings
This dialog box enables you to define text and background color settings
to help differentiate between the compared objects.

Object Repository Merge Tool
QTP enables you to merge two shared object repositories into a single
shared object repository using the Object Repository Merge Tool.

Object Repository Merge - Conflicts
• Merging two object repositories can result in conflicts arising from similarities
between the objects they contain.
• Conflicts between objects in the primary and secondary object repositories are
resolved automatically by the Object Repository Merge Tool, according to the
default resolution settings that you can configure before performing the merge.
• Conflicts between checkpoint or output value objects with the same name but
different content are always resolved by merging both objects into the new
repository and renaming one of them.
• The Object Repository Merge Tool also allows you to change the way the
merge was performed for each individual object that causes a conflict.
• The Object Repository Merge Tool identifies three possible conflict types:
1. Different Objects with the Same Name Conflict
2. Identical Description Different Name Conflict (Test Objects Only)
3. Similar Description Conflict (Test Objects Only)

Object Repository Merge Tool - Settings Dialog Box
• The Object Repository Merge Tool uses predefined settings when merging
object repositories or when updating a shared object repository from local
object repositories.
• You can change these settings at any time. After you change the settings, all
new merges are performed according to the new settings.
• The Settings dialog box contains the following tabs:
Resolution Tab. Enables you to configure how the Object Repository Merge
Tool deals with conflicting objects in the primary and secondary object
repositories (or local and shared object repositories when updating a shared
object repository from local object repositories).
Colors Tab. Enables you to specify the text color of the object names that
are displayed in the target object repository.

Object Repository Merge Tool - Settings Dialog Box
(contd)….

Object Repository Merge Tool - Filter

Object Repository Merge Tool - Statistics

Object Repository Merge Tool - Resolution

Smart Identification - Overview
 If UFT is unable to find any object that matches the learned object description, or if it
finds more than one object that fits the description, then UFT ignores the learned
description, and uses the Smart Identification mechanism (if defined and enabled) to try
to identify the object.
 The Smart Identification dialog box enables you to create and modify the Smart
Identification definition that UFT uses for a selected test object class. Configuring
Smart Identification properties enables you to help UFT identify objects in your
application, even if some of the properties in the object's learned description have
changed.
 Smart identification is not relevant for Insight and virtual test objects.
 The Smart Identification mechanism uses two types of properties:
 Base Filter Properties. The most fundamental properties of a particular test
object class; those whose values cannot be changed without changing the
essence of the original object. For example, if a Web link's tag was changed from
<A> to any other value, you could no longer call it the same object.
 Optional Filter Properties. Other properties that can help identify objects of a
particular class. These properties are unlikely to change on a regular basis, but
can be ignored if they are no longer applicable.

Smart Identification - Process
1. UFT "forgets" the learned test object description and creates a new object candidate list
containing the objects (within the object's parent object) that match all of the properties
defined in the Base Filter Properties list.
2. UFT filters out any object in the object candidate list that does not match the first
property listed in the Optional Filter Properties list. The remaining objects become the new
object candidate list.
3. UFT evaluates the new object candidate list:
• If the new object candidate list still has more than one object, UFT uses the new
(smaller) object candidate list to repeat step 2 for the next optional filter property in the
list.
• If the new object candidate list is empty, UFT ignores this optional filter property,
returns to the previous object candidate list, and repeats step 2 for the next optional
filter property in the list.
• If the object candidate list contains exactly one object, then UFT concludes that
it has identified the object and performs the statement containing the object.

Smart Identification – Test Result
 If the learned description does not enable UFT
to identify a specified object in a step, and a
Smart Identification definition is defined (and
enabled) for the object, then UFT tries to
identify the object using the Smart Identification
mechanism.
 If UFT successfully uses Smart Identification to
find an object after no object matches the
learned description, the step is assigned a
Warning status in the Run Results, and the
result details for the step indicate that the Smart
Identification mechanism was used.
 If the Smart Identification mechanism cannot
successfully identify the object, UFT uses the
learned description plus the ordinal identifier to
identify the object. If the object is still not
identified, the test or component fails and a
normal failed step is displayed in the results.

Enabling smart Identification
Step 1 : Navigate to "Tools" -> "Object Identification". Object Identification Dialog Opens.
Step 2 : Choose the Environment, Object Class and Turn ON "Enable Smart Identification"
as shown below:

Enabling smart Identification – (Contd …)
Step 3 : Click Configure and choosing the base and Optional Filter Properties.
Step 3.1 : Add Properties in Base Properties apart
from the Default one and also add/remove Optional
Filter Properties. Please Note that Same properties
cannot be part of both Mandatory and Assistive
Properties and click "OK".

Step 4 : Verifying if the Smart Identification is Enabled after Adding object of that type in
the Object Repository. Smart Identification is Set to TRUE. We can also make it False in
case we don’t want to enable Smart Identification.

Step 5 : We can even disable a test Level by applying at test script level under "Settings"
of "File" Menu as shown below:

Step 6 : If the Smart Identification is disabled as per Step# 6 then it wont apply smart
identification for any object during script execution.
Step 7 : In case objects are added with Smart Identification as Off, QTP won't use Smart
Identification for recognizing in future, even though we have enabled it afterwards.

Sample Mock Test Set 1
Serial Number Question Answer Reponse
Total correct Percentage Correct Response
1
Can we add external library files in QTP?
A. No
B. Yes 72 15.28% 11
2
What is the shortcut key to open a Step Generator
A) F2
B) F5
C) F6
D) F7
3
When you create a test, it includes ..... action.
A) Single
B) Unlimited
C) Three
D) Multiple
4
You can also encrypt strings in Data Table cells using the ......... option in the Data
Table menu.
A) Decrypt
B) Encrypt
C) Encrypt Code
D) Decrypt Code
5
Quick Test saves the object repository with a ..... extension in the specified location
A) .vsr
B) .tsr
C) .lsr
D) .qsr
6
What can you use to handle unpredictable testing exceptions?
A. A Do Loop
B. Recovery Scenario
C. IF THEN statement
D. Selectase statement
7
Using the Object Spy, you can view
A) the run-time or test object properties and methods of any object in an open
application.
B) the run-time or test object properties of any object in an open application.
C) the test object properties and methods of any object in an open application.
D) the run-time object properties and methods of any object in an open application A TRUE
8
When you modify the name of an object in the local object repository, the name is
automatically updated in ....... for all occurrences of the object..
A) in the Keyword View
B) in the Expert View
C) Both Keyword and Expert View
D) Changing name of an object doest not effect keyword or expert view
9
For opening the QuickTest Professional Help we can use.......
A) F3
B) F5
C) F1
D) F2
10
An Item column can be any of the following:
A) A test object
B) A statement like Dim
C) A step generated by step generator
D) All of above
11
There are .........object type filters in Object spy dialog box.
A) Two
B) Three
C) Four
D) Five
12
The Operation cell in the keyword view specifies the operation to be performed on
the item listed in the......... Column
A) Operation
B) Documentation
C) Item
D) Value
Section 2
Result
Section 1
Right click on below object and select open to access the test

Sample Mock Test Set 2
Serial Number Question Answer Reponse
Total correct Percentage Correct Response
1
The ________________ displays the open documents side-by-side.
A. Tile Vertically
B. Tile Horizontally
C. Cascade
D. Tile Cascade
72 0.00% 0
2
Shortcut Key for closing all open Function Libraries in one go.
A. Ctrl+Alt+C
B. Shift+A+C
B. Shift+N
D. None of these
3
While working with the Keyword View, you can _________ steps to move them to a
different location in a test or in an action
A. Copy and Paste
B. Cut and Paste
C. Drag and drop
D. Both A. and C.
4
You can manage the test actions and the test or function library steps using the
_________ menu commands
A. File
B. Edit
C. Automation
D. Tools
5
What are expected values in HP QuickTest Professional?
A. The values recorded during a test run and compared with original values within
test objects
B. The values contained in the "expected results" property of each test object
C. The values predefined as the expected results of an unsuccessful test run
D. The values captured during recording and used in checkpoints as reference values
6
Which type of visual cue is easy to test with HP QuickTest Professional and requires
a large amount of time to verify manually?
A. Content of an image
B. Existence of an image
C. Grayed-out field
D. Text attachment
7
What are the predefined Web Event Recording Configurations in HP QuickTest
Professional? (Select three.)
A. Low
B. Basic
C. Medium
D. Intermediate
E. High
F. Advanced
8
Before automating a test, you decide to create a library of actions to be reused to
achieve testing goals.
Which elements are critical for recording the different combinations of actions?
A. Starting and ending parameters
B. Input and output conditions
C. Initial and end conditions
D. Visual and implied cues
Result
Section 1

Sample Question bank
HP QTP Certification - 500 Sample Questions
Q. 1: You can manage the test actions and the test or function library steps using the
_________ menu commands
A. File
B. Edit
C. Automation
D. Tools
Q. 2: To expand all the steps in the keyword view which option you would use from the View
menu.
A. Expand
B. Expand All
C. Expand Items
D. Expand Rows
Q. 3: What is the shortcut key to open a Step Generator?
A. F2
B. F5
C. F6
D. F7
Q. 4: Function Definition Generator in found in which menu option.
A. File
B. Tools
C. Insert
D. View
Q. 5: The shortcut keys for Record, Stop and Run respectively are
A. F3, F4, F5
B. F4, F3, F5
C. F4, F5, F3
D. F3, F5, F4
Q. 6: What is the shortcut key for opening an Object Repository?
A. Alt+R
B. Shift+R
C. Ctrl+R
D. Shift+O+R
Q. 7: Shortcut key to Insert/Remove a breakpoint is
A. F9
B. F8
C. Ctrl+b
D. Shift+b

Reference
HP QTP 11.0 User manual Click on file

THANKS
Presented by Vishwaprakash Sahoo
Vishwaprakash.s@gmail.com

Qtp certification training_material

Recommended

Recommended

More Related Content

What's hot

What's hot (18)

Similar to Qtp certification training_material

Similar to Qtp certification training_material (20)

Recently uploaded

Recently uploaded (20)

Qtp certification training_material