Quick Test Professional 9.

Prepared

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

Testing Process

Planning Creating Tests Running Tests Analyzing Results

Planning
Before beginning to create a test, you should plan it and prepare the required infrastructure. For example, determine the functionality you want to test, and decide which information you want to check during the test run.

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 another user might perform when using your application or Web site. You can enhance the testing process by modifying your test with special testing options and/or with programming statements.

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.

Running Tests
Run your test to check your application. Run your test to debug it.

Analyzing Results

View the results in the Test Results window. Report defects detected during a run session.

Quick Test Window

Keyword View
Enables you to create and view your test steps in a keyword driven tabular format. For each row in the Keyword View, QuickTest displays a corresponding line of script in the Expert View.

Expert View
In the Expert View, QuickTest displays each operation performed on your application in the form of a script, comprised of VBScript statements. The Expert View is a script editor with many script editing capabilities. For each object and method in an Expert View statement, a corresponding row exists in the Keyword View.

Active Screen
The Active Screen provides a snapshot of your application as it appeared when you performed a certain step during a recording session. Additionally, depending on the Active Screen capture options that you used while recording, the page displayed in the Active Screen can contain detailed property information about each object displayed on the page.

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, QuickTest automatically checks for syntax errors in your script, and shows them in the Information pane. If the Information pane is not currently displayed, QuickTest automatically opens it when a syntax error is detected.

Data Table
The Data Table contains one Global tab plus an additional tab for each action, or test step grouping, in your test. The Data Table assists you in parameterize your test. The Data Table is a Microsoft Excel-like sheet with columns and rows representing the data applicable to your test.

Planning and Preparing to Create a Test

Determine the functionality you want to test. Decide which information you want to check during the test. Decide how you want to organize and manage your object repository. Determine whether you need to create any new user defined functions or whether you should associate existing function libraries with your test.

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 by the multiple tests. Local OR stores objects in a file that is associated with one particular action, so that only that action can access the stored objects. By default, object information is stored in a local OR. We can transfer local objects to shared objects and we also use the combination of both. It is preferred to use the stored object repository as it can be used for multiple actions.

CheckPoints

Understanding Checkpoints
A checkpoint is a verification point that compares a current value for a specified property with the expected value for that property. This enables you to identify whether your Web site or application is functioning correctly.

Types of Checkpoints:
Standard Checkpoint Bitmap Checkpoint Table Checkpoint Text Checkpoint Accessibility Checkpoint Page Checkpoint Database Checkpoint XML Checkpoint

Standard Checkpoints checks the property value of an object in your application. 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 a bitmap. These are used to check the appearance of the elements in the application. We will capture the area of the object to be checked and will compare 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 your application. XML Checkpoint checks the data content of XML documents in XML files or XML documents in web pages.

Data Driven Tests

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

Elements of Data Driven Test

Recorded Test Script Parameter (s) A parameter is a variable which replaces the recorded value in the script. At run time, quick test substitutes a value from the data source for the parameter. Data Source The location of data that Quick Test will use to supply the parameter.

Debug Viewer

Debug Viewer
Debug Viewer is used to view, set or modify the current value of the objects or variables in the test or function library. When the test stops at the breakpoint, user can select the debug option. Debug Viewer has 3 tabs: Watch Tab Variables Tab Command

Watch Tab

This tab is used to view the current value of any variable or VB script object in the test or function library. Quick test automatically updates the watch tab with the current value 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 variable in the name column and press Enter to view the current value in the value column.

Variable Tab

Quick Test automatically displays the current value of all the variables in the current action or function in the variable tab. As the test progresses, quick test will automatically updates the value 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 the test or function library. When the run continues, then quick test uses the value that user sets.

Thank You!