6739392 quick test professional (1)

8/6/2019 6739392 Quick Test Professional (1)

1/31

Quick Test

Professional 9.0

Prepared


2/31

Introduction

Welcome to Mercury Quick Test Professional,the advanced solution for functional test andregression test automation.Quick Test Professional enables you to teststandard Windows applications, Web objects,ActiveX controls and Visual Basic applications.


3/31


4/31

Planning

Creating Tests

Running Tests

Analyzing Results


5/31

Planning

Before beginning to create a test, you shouldplan it and prepare the required infrastructure.

For example, determine the functionality youwant to test, and decide which information youwant to check during the test run.


6/31

Creating Tests

Every test is composed of one or more actions.At its most basic level, each action contains steps

that duplicate the activities that you or anotheruser might perform when using your applicationor Web site. You can enhance the testing processby modifying your test with special testing

options and/or with programming statements.


7/31

When you create your test:

Add steps to your test:

1. Build the object repository.

2. Record a session on your application.

Insert checkpoints.

Broaden the scope of your test by replacing fixed values

with parameters.

Add user defined functions by creating function libraries.


8/31

Running Tests

Run your test to check your application.

Run your test to debug it.


9/31

Analyzing Results

View the results in the Test Results window.

Report defects detected during a run session.


10/31

Quick Test Window


11/31

Keyword View

Enables you to create and view your test steps ina keyword driven tabular format.

For each row in the Keyword View, QuickTestdisplays a corresponding line of script in theExpert View.


12/31

Expert View

In the Expert View, QuickTest displays eachoperation performed on your application in the

form of a script, comprised of VBScriptstatements. The Expert View is a script editorwith many script editing capabilities. For eachobject and method in an Expert View statement,

a corresponding row exists in the KeywordView.


13/31

Active Screen

The Active Screen provides a snapshot of yourapplication as it appeared when you performed

a certain step during a recording session.Additionally, depending on the Active Screencapture options that you used while recording,the page displayed in the Active Screen can

contain detailed property information abouteach object displayed on the page.


14/31

Information Pane

The Information pane provides a list of syntaxerrors in your test or function library scripts.

When you switch from the Expert View to theKeyword View, QuickTest automatically checksfor syntax errors in your script, and shows themin the Information pane. If the Information pane

is not currently displayed, QuickTestautomatically opens it when a syntax error isdetected.


15/31

Data Table

The Data Table contains one Global tab plus anadditional tab for each action, or test stepgrouping, in your test. The Data Table assistsyou in parameterize your test. The Data Table isa Microsoft Excel-like sheet with columns androws representing the data applicable to yourtest.


16/31

Planning and

Preparing to Create aTest


17/31

Determine the functionality you want to test.

Decide which information you want to checkduring the test.

Decide how you want to organize and manageyour object repository.

Determine whether you need to create any new

user defined functions or whether you shouldassociate existing function libraries with yourtest.


18/31

Identifying Objects

Object information is saved in the object repository file.QTP has two object repository files: local and shared.

Shared OR stores objects in a file that can be accessed bythe multiple tests. Local OR stores objects in a file that is associated with

one particular action, so that only that action can accessthe stored objects.

By default, object information is stored in a local OR. Wecan transfer local objects to shared objects and we alsouse the combination of both. It is preferred to use thestored object repository as it can be used for multipleactions.


19/31

CheckPoints


20/31

Understanding Checkpoints

A checkpoint is a verification point thatcompares a current value for a specified

property with the expected value for thatproperty. This enables you to identify whetheryour Web site or application is functioningcorrectly.


21/31

Types of Checkpoints:

Standard Checkpoint

Bitmap Checkpoint

Table Checkpoint Text Checkpoint

Accessibility Checkpoint

Page Checkpoint Database Checkpoint

XML Checkpoint


22/31

Standard Checkpoints checks the property value of an object in yourapplication. It checks a variety of objects such as buttons, radio buttons,combo boxes, lists etc.

Bitmap Checkpoints checks an area of your web page or application as abitmap. These are used to check the appearance of the elements in theapplication. We will capture the area of the object to be checked and willcompare it with the run time area of the object.

Table Checkpoint checks information within a table. Text Checkpoint checks that text string is displayed in the appropriate

place. Accessibility Checkpoint identifies areas of your web site that may not

conform to W3C web content accessibility guidelines. Page Checkpoint checks the characteristics of a web page. E.g. how long a

web page takes to load or whether the page contains broken links. Database Checkpoint checks the contents of a database accessed by yourapplication.

XML Checkpoint checks the data content of XML documents in XML filesor XML documents in web pages.


23/31

Data Driven Tests


24/31

Data Driven Tests A test that runs one set of user actions with

multiple input values. Data driving allows one script to test AUT with

many sets of data.

Benefits:

Increased Testing coverage Test boundary conditions Test good data and bad data


25/31

Elements of Data Driven Test

Recorded Test Script Parameter (s)

A parameter is a variable which replaces therecorded value in the script.At run time, quick test substitutes a value fromthe data source for the parameter.

Data SourceThe location of data that Quick Test will use tosupply the parameter.


26/31

Debug Viewer


27/31

Debug Viewer

Debug Viewer is used to view, set or modify thecurrent value of the objects or variables in the test orfunction library.

When the test stops at the breakpoint, user can selectthe debug option.

Debug Viewer has 3 tabs: Watch Tab

Variables Tab Command


28/31

Watch Tab

This tab is used to view the current value of any variable or VBscript object in the test or function library.

Quick test automatically updates the watch tab with the currentvalue of the object or variable whose value changes.

Steps for adding an expression to the watch tab: Click the expression and debug -> Add to watch. Click the expression and press CTRL+T Right click the expression and choose add to watch from the

context menu.

In the watch tab, paste or type the name of the object or variablein the name column and press Enter to view the current value inthe value column.


29/31

Variable Tab

Quick Test automatically displays the current value of all thevariables in the current action or function in the variable tab.

As the test progresses, quick test will automatically updates thevalue displayed in variable tab.

User can also change the value of the variable manually during the

breakpoint pause.

Command Tab

Command tab is used to execute a line of script in order to set or

modify the current value of the variable or VB script object in thetest or function library. When the run continues, then quick test uses the value that user

sets.


30/31


31/31

Thank You!

6739392 quick test professional (1)

Documents