qtp - automation testing training

8/14/2019 QTP - Automation Testing Training

1/89


2/89

Session Objectives

Introduction to Automation

Benefits of Automated Testing

Automated Testing Process Introduction to QTP and its Salient Features

Environment Supported


3/89

Introduction to Automation

Drawbacks of Manual testing

- Manual testing is time-consuming and tedious- Requiring a heavy investment in human resources- Time constraints often make it impossible to manually

test every feature thoroughly before the application is

released

- Low reliability

Manual TestingManual Testing


4/89

Benefits of Automated Testing

Why Automation

- Fast

- Reliable

- Repeatable

- Programmable

- Comprehensive

- Reusable

Automated TestingAutomated Testing


5/89

The following XL sheet give you the difference inTime taken for Manual testing and Automation

Testing.

Sr.No. Business Process

Script

Name

No of

Conditions

No of

Conditions

utomated

Effort (in

hours) for

utomation

Effort (in seconds)

for Manual

Running of all the

conditions

Time Taking

for Running

(in Seconds)

for one

iteration

1 Sales Order Processing S001 32 32 30.4 1500 420

2 Reversal Process S002 7 7 6.65 298 123

3 BOM and Pallets S003 8 8 7.6 512 240

4 Shipment S004 4 4 3.8 395 120

5 POD & X-DOCS S005 10 10 9.5 714 182

6 Free Promotions Goods S006 4 4 3.8 388 124

7 Crate Material S007 3 3 2.85 445 148

8 Generation of Requirement S008 1 1 0.95 422 210

9 Batch Split & Invoice Summary S009 2 2 1.9 630 101

10 Inter company Sales S010 5 5 4.75 555 185

11 Out of Scope 40 0 0

10

Total 116 76 72.2 5859 1853

Sr.No. Business Process

Script

Name

No of

Conditions

No. of

Condtions

utomated

Effort (in

hours) for

utomation

Effort (in seconds)

for Manual

Running of all the

conditions

Time Taking

for Running

(in Seconds)

for one

iteration

1 Rebate Agreement Processing R001 28 28 26.6 1200 360

2 Out of Scope 2 0 0

Total 30 28 26.6 1200 360

Sales Process

RebatesProcess


6/89

Which Test Cases to Automate?

Tests that need to be run for every build of theapplication (sanity check, regression test)

Tests that use multiple data values for the same actions

(data driven tests) Stress/load testing

Tests requiring a great deal of precision


7/89

Which Test Cases Not 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


8/89

Leading Automation Tools available in the

Market For Functional testing

WinRunner

QTP

Rational Robot

Silk Test

QA Run


9/89

Automated Testing Process

Automated testing involves three main steps

Creating Script(s)

Executing Script(s)

Analyzing Result(s)


10/89

Advantages of QTP over Win runner

QTP has user-friendly Browser, At a Glance we canhave a look of Scripts, Active Screen and the Data XL

Sheet. QTP uses VB Script while win runner uses TSL which is

C language based

QTP has Recovery Manager

QTP generates output values and these can be used asinput values to other Objects


11/89


12/89

Introduction to QTP

Quick Test Professional is the flagship functional testingtool from Mercury Interactive.

It is an icon based tool, which automates the functional

& regression testing of an application. QTP is easier to use and implement for both technical &

non technical testers in comparison to other functionaltesting tools available.

Available versions are QTP 6.0 , 6.5,8.0 and 8.2


13/89

Salient Features

Its Active Screen technology offers a Point-and-checkinterface for accessing & interacting with thecomponents of the application under test.

QTP produces an Icon-Based test tree in which eachbranch represents a step in the business process Testers can view and edit their test using either the tree

view, an Icon-Based representation, or the expert View,which reveals the VBScript test that QTP automaticallygenerates.

QTP can automatically introduce Checkpoints


14/89

Salient Features

During execution testers can manually insert severaltypes of check points to verify that the objects continueto behave as expected. These check points are shown inthe presentation in the later stage

Testers are able to record their tests so that each action,or step in the business process are modular & reusable.

When application under test changes, testers can updateObject Repository, thus the change made is then

propagated across all the scripts that reference to thisobject EX: In the Authentication screen when the name of

the button is changed to Sign In form Login, Justmake an update in the Object Repository.


15/89

Salient Features

After running a test QTP displays the results in a tressstructure and in clear visual reports

Scripting Language is VBScript which is easy to use ,understand and program even complex functionalities withease..

Library files contains VBScript functions andsubroutines that can be added to the test.

Support Modern Development Environment.


16/89

QuickTest testing process

The QuickTest testing process consists of 7 main phases:

1. Preparing to record

2. Recording a session on your application3. Enhancing your test

4. Debugging your test

5. Running your test

6. Analyzing the test results

7. Reporting defects


17/89

AddIn Manager Default

ActiveX

VisualBasic

Web

Additional

Java

Oracle

PeopleSoft

.Net

Terminal Emulator

Sap, Siebel & Web services


18/89

Environments Supported

Basic Web Technologies HTML DHTML

XML Browsers

Netscape Internet Explorer AOL

Advanced Web Technologies JavaScript Java ActiveX


19/89


Multimedia Technologies Flash RealAudio/Real Video

MS Media Player ERP Solutions

mySAP.com Siebel 2001 Oracle PeopleSoft

.NET Win Forms Web Forms NET Control


20/89


Web Services

XML

WSDL

Operating Systems

Windows XP/2003

Windows 2000

Windows 98

Windows NT

Windows ME


21/89


Terminal Emulators

3270

5250

VT100

Languages

European

Japanese

Chinese (traditional and simplified)

Korean


22/89

Environments not Supported

Custom C/S PowerBuilder Forte Delphi Centura Stingray Smalltalk

ERP/CRM Baan PeopleSoft Windows Siebel 5, 6 GUI Clients Oracle GUI Forms


23/89

QTP Screen


24/89

Important Toolbars

Test toolbar: containing buttons to assist you in thetesting process(ex: record,Run..)

Debug toolbar: containing buttons to assist you in

debugging your test Action toolbar: containing buttons and a list of actions,enabling you to view the details of an individual action orthe entire test flow

Test pane: containing two tabs to view your testtheKeyword View and the Expert View

TestDetails pane : containing the Active Screen Data Table: containing two or more tabs to assist you in

parameterizing your testGlobal and one tab for eachAction


25/89

What you need to Know in QTP?

How are the objects recognized? What is Object Repository? What is Object Recognition configuration? What is Active Screen? What is Keyword View and Expert View? What are Actions? What are the checkpoints available?

Output Values

Synchronization Point

Data Driven Test? Transaction Response Time Exception Handling

Reporting


26/89

Recording Modes in QTP

Normal(This mode is the default and takes full advantage ofQuick Test's test object model, recognizing the objects in your

application regardless of their location on the screen)

Analog Recording (enables you to records the exact mouseand keyboard operations you perform in relation to either thescreen or the application window. In this recording mode, QuickTest record and tracks every movement of the mouse as you

drag the mouse around a screen or window. User cannot editanalog recording steps from within Quick Test)


27/89

Recording Modes in QTP

Low Level Recording (enables you to record on any object inyour application, whether or not Quick Test recognizes the

specific object or the specific operation. This mode records atthe object level and records all run-time objects as Window orWin Object test objects. Use low-level Recording for Recordingtests in an environment or on an object not recognized byQuick Test. You can also use low-level Recording if the exactcoordinates of the object are important for your test.)


28/89


How are the objects recognized? What is Object Repository? What is Object Recognition configuration? What is Active Screen? What is Keyword View and Expert View? What are Actions? What are the checkpoints available?

Output Values

Synchronization Point

Data Driven Test? Transaction Response Time Exception Handling

Reporting


29/89

Object Repository

Object Repository acts as a translator between QTPscript and the Operating System ( similar to GUI mapconcept in win runner).

QTP stores information it learns about a window or anobject in object repository

When QTP runs a test, it uses the object repository tolocate objects. QTP reads an objects description in therepository and then looks for an object with the sameproperties in the application under test.


30/89

How QTP Stores Objects

ObjectRepository

QTP

TEST SCRIPT

Generates Script Add objects using

object

identification

settings


31/89

Object Repository

Types of Object Repositories

Per Action Object Repository

Shared Object Repository


32/89

Object Repository Per Action

ObjectRepository

TEST 1

ACTION 1

ACTION 2

TEST 2

ACTION 1

ACTION 2

Object

Repository

ObjectRepository

ObjectRepository


33/89


TEST 1

ACTION 1

ACTION 2

TEST 2

ACTION 1

ACTION 2

Object

Repository


34/89

Per Action vs SharedObject Repository

Per Action Object Repository

Separate action repositoryfor each action.

If an object description

changes, you need tomodify the object in everyaction repository using thatobject.

No need for any ObjectRepository administrator.

Preferred method if

application wont changeduring renovation Default Object Repository.

Preferable for novice QTPusers.


can use the same sharedobject repository file formultiple tests.

If an object descriptionchanges, you only have tomodify in the shared ObjectRepository all tests willplayback properly.

Requires Shared objectrepository creation and

maintenance. Crucial if application may

change during renovation Most commonly used across

Automation projects.


35/89


How are the objects recognized? What is Object Repository? What is Object Recognition configuration? What is Active Screen?

What is Keyword View and Expert View? What are Actions? What are the checkpoints available?

Output Values

Synchronization Point Data Driven Test? Transaction Response Time Exception Handling

Reporting


36/89

Object Recognition configuration

To identify objects uniquely, object identificationconfiguration can be done. User can configureMandatory,Assistive properties and ordinal identifier

Examples:

List Box

Combo Box

Text Box

Text Area


37/89

Smart Object Identification

Smart Object Identification to Ensure Successful TestExecution

A sophisticated object recognition mechanism allowstests to automatically recover when object properties arenot found during execution. Quick Test now evaluatesapplication object properties upon test playback, and canmake decisions based on logical property matches, evenif the recorded object properties are not present.


38/89

Smart Object Identification

Base filter propertiesThe most fundamentalproperties of a particular test object class; those whosevalues cannot be changed without changing the essence

of the original object. For example, if a Web link's tagwas changed from to any other value, you could nolonger call it the same object.

Optional filter propertiesOther properties that canhelp identify objects of a particular class as they areunlikely to change on a regular basis, but which can be

ignored if they are no longer applicable How does Smart Identification process work?


39/89




Output Values


Reporting


40/89

What is Active Screen?

While recording the screen is captured and stored. In thetool the same can be seen as Active Screen

The same can be updated by using Change ActiveScreen Option


41/89




Output Values


Reporting


42/89

Script View

Keyword View

Expert View


43/89

Keyword View


44/89

Expert View


45/89




Output Values


Reporting


46/89

What are Actions?

Actions help divide your test into logical units

Group of Statements to perform certain action

Actions can be nested

Multiple actions can be called in a single test

Splitting Actions

Calling Actions

Using Action Parameters

Impact on Object Repository


47/89

Actions

Three Types

Nonreusable

Re-usable External


48/89

Actions

Actions can divide a test into several distinct businessProcesses.

Each actions signifies a logical independent test.

To divide a test into actions you can Insert a New Action

Split an existing action into two Actions

Insert a copy of an existing Action

Insert a call to an existing Action

In this way several actions can be integrated to eachother within the test or across different tests logically.


49/89




Output Values


Reporting


50/89

Checkpoints

A checkpoint is a step in your test that compares the actualvalues of a specified object property to an expectedvalue of the same property

Like,

Verify text in status bar

Verify value in a grid

Verify bitmaps (Tick mark in Release strategy )


51/89

Checkpoints

Various Checkpoints are available

Text / Text Area Checkpoint

Bitmap Checkpoint

Database Checkpoint XML Checkpoint(File/Webpage)

Standard Checkpoint(Page/Table/Image/object)

Accessibility Checkpoint


52/89




Output Values


Reporting


53/89

Output Values

An Output value is a step in which one or more valuesare captured at a specific point in the test

Can capture status bar messages

Can capture object properties and text

Can store the values in a variable or table Text / Text Area Output Value

Bitmap Output Value Database Output Value

XML Output Value(File/Webpage)

Standard Output Value


54/89




Output Values


Reporting


55/89

What is a Synchronization Point?

A synchronization point is a line in the test scriptthat instructs QTP to wait for a certain responsefrom the application during playback.


56/89

Why Synchronize?

Without synchronizationpoint

With synchronization point

Inputs datato AUT

A eptsinput

Run script

Sends data todatabase server

Attemptsnext step

Waits forserver;cannot

continue

Scriptfails

Sends data todatabase server

Waits

ContinuesClient affirmstransaction iscomplete

Inputs data

to AUT

Accepts

input

Run script


57/89

Process To Add Synchronization Points

Locate the lines in the script to insert the synchronizationpoint

In Quick Test choose Insert > Step > SynchronizationPoint. The mouse pointer turns into a pointing hand.This should be done while recording.

Using the Hand Pointer click on the object toSynchronize.

Add Synchronization Point dialog box opens.


58/89

SynchronizationSynchronization

Select the Property name and its corresponding value whichyou want to use for the synchronization point.

Enter the synchronization point timeout (in milliseconds) andClick OK. A Wait Property step is added to your test.

For e.g. for this case the step inserted in the script will be

Dialog (Login) . WaitProperty "enabled", 1, 10000


59/89




Output Values


Reporting


60/89

Data Driven Testing

QTP supports Data Driven Testing

Can use the Data Driver Wizard to parameterize the tests

Stores data file with extension .XL Two types of sheets within the data table Global and

Action

Data in Global is available across all actions in the test

Data in Action is available only to that action


61/89

Parameterization

Parameterization allows us to pick different values at runtime.

Reduces Time and Effort.

Usage of data drivers allow us to use the same data forvarious input boxes.

Parameterization can also be done for checkpoints.


62/89




Output Values

Synchronization Point Data Driven Test?

Transaction Response Time Exception Handling

Reporting


63/89

Transaction Response Time

Transaction Response Time is used to measure theresponse 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)


64/89




Output Values



Reporting


65/89

Recovery scenarios

QTP can recover from unexpected events and/ or errors

Control can be transferred to a function

Useful, when running unattended

Every Script has at least one recovery scenario

Generic recovery scenario naming convention isg

Script specific recovery scenarios naming convention

is _


66/89

Recovery scenarios In QTP

What is Recovery Scenario

How to Implement Recovery Scenario

Types of Recovery Scenario

Advantage of Recovery Scenario

Disadvantage of Recovery Scenario


67/89

What is Recovery Scenario

Recovery Scenario is used to control the execution flowof QTP script.

To Control the unexpected event or action perform bythe application which we are going to automate.


68/89

Recovery Scenario

Unexpected events, errors, popup window, message, linkand application crashes during a test run can disrupt

your test and distort test results. This is a problemparticularly when running tests unattendedthe test issuspended until you perform the action needed torecover.


69/89

How to Implement Recovery Scenario.

In QTP the Recovery Scenario Manager provides a wizardthat guides you through the process of defining a

recovery scenarioa definition of an unexpected eventand the operation's necessary to recover the test run.


70/89

How to Implement Recovery Scenario.

Record the Error on which you want to create recovery.

In QTP go to Tools Menu Option -> select the RecoveryScenario Manager.


71/89

Recovery Scenario Manager


72/89

Recovery Event


73/89

Recovery Condition


74/89

Recovery Operation


75/89

Run Option


76/89

Save The Recovery Scenario


77/89

Tip

After you have created recovery scenarios, you canassociate one or more scenarios with a test in order to

instruct QuickTest to perform the recovery scenario'sduring the test run if a trigger event occurs. TheRecovery tab of the Test Settings dialog box lists all the

recovery scenarios associated with the current test.


78/89

To add a recovery scenario to a test


79/89

Advantage of Recovery Scenario

Control the Execution flow of script.

Handle unexpected behavior of application.

User define Error Message.


80/89

Settings

When we call Recovery scenario with On Every stepoption scrip execution become slow. Call only onError.


81/89




Output Values



Reporting


82/89

Execute Script

Script can be executed in two ways

Run

Select Test->Run

Run from Step

Select Test->Run from Step


83/89

Test Run

Where the Test Results are stored

Two ways

New folder is created for each run

Temp folder overwrites last run results

E.g..

T:\QTP_SCRIPTS_FINAL\S007_015\Res1

C:\DOCUME~1\SU2693\LOCALS~1\Temp\TempResults


84/89

Test Run


85/89

Analyze Result's

Structure of a Test Result log

Results at an overall level and at step level

Results at action level rolled up to get summary of

results

Screen shots help you to verify the flow

Screen shots available to identify the failures

Run time data is visible for debugging the failures


86/89

Test Results

QTP Test/Step Outcome Passed

Expected Vs actual is same Failed

Expected Vs actual is different Done

Step has been executed when unable to execute, marks the step as failed

Warning

Step has been executed but QTP logs a message


87/89

Test Results

How to view the Test Results

Select Test->Results

How to check the results of the past runs

Select Start->QTP->Test Results Viewer

How to delete the past test results

Select Start->QTP->Tools-> Test Results DeletionTool


88/89




Output Values



Reporting


89/89

Any Questions?

?Thanks

qtp - automation testing training

Documents