TCC QTP Overview

8/2/2019 TCC QTP Overview

1/29

QuickTestProfessionalOverview

Anju K John


2/29

SAP AG 2002, Test Partner: Srinivasa GV, Jai Santosh,

Introduction to QTP

QuickTest Professional is an advanced solution for functional test andregression test automation.

QuickTest Professional enables you to test:

Standard Windows applications

Web objects

Visual Basic applications, etc.

You can also acquire additional QuickTest add-ins for a number of specialenvironments (such as Java, Oracle, SAP solutions, .NET, Siebel,PeopleSoft, Web services, etc.)


3/29


QuickTest User Interface


4/29


QuickTest Workflow


5/29


QuickTest Workflow - Prepare


6/29


Prepare to Record

Check for stability.

Determine who is creating which test.

Execute the test case steps manually.

Determine the initial and end conditions of the test.

Check your data.

Standardize naming conventions.


7/29


Launching QuickTest Professional

Select Add-Ins.

Set QuickTest Professional Options.

Establish the appropriate Record and Run Settings for the test.


8/29


QuickTest Workflow Create a Basic Test


9/29


Record and Playback

In this section, the following will be discussed:

Create a basic Test script.

Save the Test script.

Run the Test script.

Analyzing the Test Results.


10/29


Create a Basic Test script (Record) & Save

A basic test consists of recorded user actions on the application.

Basic test is bare of any enhancements.

The test script can be saved to any location specified.


11/29


Recording Mode

Normal Recording - Records the objects in your application and the

operations performed on them. This mode is the default.

Analog Recording - Record the exact mouse and keyboard operations.

Low level Recording - This mode records at the object level and

records all run-time objects as Window or WinObject test objects.


12/29


Playback (Run the script)

Running the already recorded script.

Playback without error establishes that the test is ready for further

automation and enhancement.


13/29


Analyzing the Test Results

When QuickTest finishes running the test, the Test Results window

opens.

The Test Results window displays all aspects of the run session,

including:A high-level results overview report (pass/fail status)

The data used in all runs

An expandable tree of the steps, specifying exactly where application failures

occurred

The exact locations in the test where failures occurred

Application snapshots that highlight any discrepancies, for each stage of the

test


14/29


QuickTest Object Identification

In this section, the following will be discussed:

Test Object model

How QuickTest identifies objects while Recording

How QuickTest identifies objects during Run session

Test Object and Run-time Object

Object Repository

Object Spy


15/29


How to recognize an object?


16/29


Test Object Model

The test object model is a large set of object types or classes that

QuickTest uses to represent the objects in your application.

Each test object class has a list of properties that can uniquely identify

objects of that class and a set of relevant methods that QuickTest canrecord for it.


17/29


How QuickTest identifies objects while Recording

Identify the object class and store it as a TEST OBJECT.

For each test object class, QuickTest has a list of mandatory properties that

it always learns.

If mandatory properties are not enough to uniquely identify the object,

QuickTest adds assistive properties, one by one, to the description, until it

has compiled a unique description.

If no assistive properties are available, or if those available are not sufficient to

create a unique description, QuickTest adds a special ordinal identifier, such

as the objects location on the page or in the source code, to create a unique

description.


18/29


How QuickTest identifies objects during Run Session

QuickTest searches for a Run-time object that exactly matches the

description of the test object it learned while recording.

It expects to find a perfect match for both the mandatory and any

assistive properties it used to create a unique description while recording.

If QuickTest 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

QuickTest ignores the learned description, and uses the Smart

Identification mechanism to try to identify the object.


19/29


Applying the test object model concept

When you perform an operation on your application while recording,QuickTest:

identifies the QuickTest testobject class that represents theobject on which you performed the operation and creates theappropriate test object

reads the current value of the objects properties in yourapplication

stores the list of properties and values with the test object

chooses a logicalname for the object.

records the operation that you performed on the object using theappropriate QuickTest test object method

This Test object information is stored in the Object Repository.


20/29


Object Spy

Used to view the properties of an object in an open application

The Object Spy displays:

Object hierarchy tree

Run-time object methods

Test object methods


21/29


QuickTest Workflow Enhance the Test


22/29


Synchronization

WHAT

Refers to adding a step in the Testscript that instructs QuickTest to wait

for a particular object before

proceeding to next step during

Playback.

WHY

Ensure successful playback.

WHEN

User action requires processing

time.

Can be done ONLY while

recording.


23/29


Checkpoint

A checkpoint is a verification point that compares a current value for

a specified property with the expected value for that property.

Test Results provide the most value when the test has checkpoints.

The status of each checkpoint and its details are reported Expectedresult, Actual result, Checkpoint name and the Status (Pass or Fail.)

Ch k i t T


24/29


Checkpoint Types

Di idi T t i t A ti


25/29


Dividing Tests into Actions

Actions help divide your test into logical units

An action consists of its own Test script, object Repository and Datatable.

W ki ith N A ti


26/29


Working with New Actions

You can create new actions and add calls to them during a recording

session or while designing or editing your test.

You can call the new action from your test flow as a top-level action,

or you can call the new action from within another action in your test as

a nested action.

W ki ith E i ti A ti


27/29


Working with Existing Actions

You can split an existing action into two actions.

Inserting existing Action into a test:

Call to a copy of the existing action

Call to the existing action

Inserted in read-only format.

Easier to maintain.

The action is copied as an independent non-reusable action.

Can be modified.

Call to the existing Action

Call a Copy of existing Action

P t i T t


28/29


Parameterize Tests

QuickTest enables you to expand the scope of a basic test by replacing

fixed values with parameters. This process, known as Parameterization,greatly increases the power and flexibility of your test.

Different types of parameters:

Test/Action parameters

Data table parameters

Environment variable parameters

Random number parameters

O t t V l


29/29


Output Values

QuickTest enables you to retrieve values in your test and store them as

Output values.

You can create the following categories of output values:Standard output values

Text output values

Table output values

Database output values

XML output values

You can output a value to: a test or action parameter

the run-time Data Table

an environment variable

Documents

TCC QTP Overview