WinRunner Training

Winrunner Training Objective of the Course

Understand the benefits of automated testing

To get an insight into the working of automated test tools

To use and understand the features of Winrunner

Creation of test scripts using Winrunner

Benefits of Automated Testing WinRunner Testing Process WinRunner Recording Mode Working with other Test Suite Tools

Manual Vs. Automated Testing

Manual Testing:

Is time-consuming and tedious

Requires a heavy investment in human resources

Time constraints often make it impossible to manually test every feature thoroughly before the software is released

Automated Testing:

Dramatically speed up the testing process

Creation of test scripts which check all aspects of the application

Execute these tests on each new build

Benefits of Automated Testing Fast: Run tests significantly faster than human users Reliable: Tests perform precisely the same operations each time they are run, thereby eliminating human error Repeatable: You can test how the software reacts under repeated execution of the same operations Programmable: You can program sophisticated tests that bring out hidden information from the application Comprehensive: You can build a suite of tests that covers every feature in your application Reusable: You can reuse tests on different versions of an application, even if the user interface changes

WinRunner Testing Process

1 Create the GUI Map

WinRunner must learn to recognize the objects in an application in order to run tests

The preferred way to teach WinRunner your objects depends on the GUI map mode

2 Create Tests

WinRunner writes scripts automatically when recording actions in applications

One can program directly in Mercury Interactive’s Test Script Language (TSL)

3 Debug Tests

You debug the tests to check that they operate smoothly and without interruption

WinRunner Testing Process

4 Run Tests

Run tests in Verify mode to test your application

It compares the current data of the application being tested to the expected data captured earlier

If any mismatches are found, WinRunner captures them as actual results

5 View Results

After each test run, WinRunner displays the results in a report

The report details all the major events that occurred during the run, such as checkpoints, error messages, system messages, or user messages

6 Report Defects

If a test run fails due to a defect in the application being tested it can be reported directly from the Test Results window

This information is sent via e-mail to the quality assurance manager, who tracks the defect until it is fixed

Recording Mode

Context Sensitivity

Context Sensitivity records operations in terms of GUI objects.

For e.g.

if you record a mouse click on OK button. WinRunner generates following TSL statements-

Analog Mode

Analog Mode Records the exact coordinates traveled by the mouse

For e.g.

if you record a mouse click on OK button. WinRunner generates following TSL statements

button_press (“ OK ”); move_locator_track (1); mtype ("<T110><kLeft>-"); mtype ("<kLeft>+");

Choosing a Recording Mode

Choose Context Sensitive if...

The application contains GUI objects

Exact mouse movements are not required

You plan to reuse the test in different versions of the application

Choose Analog if...

The application contains bitmap areas (such as a drawing area)

Exact mouse movements are required

Starting WinRunner

To start WinRunner, click Start > Programs > WinRunner > WinRunner

Recording User Actions

Creating a New test

Click on New Test

Recording User Actions

WinRunner Main Window

WinRunner Standard Toolbar

Recording a Test

To Record a Test in WinRunner, Select the Record Button from the Standard Toolbar

Recording a Test

Open the Application and Enter the Data

Automatic Script Generation Enter Application Data

Benefits of Automated Testing WinRunner Testing Process WinRunner Recording Mode Working with other Test Suite Tools

Working with Other Test Suite Tools WinRunner works with other Test Suite tools to provide an integrated solution for all phases of the testing process I.e. Test Planning, Test Development, GUI and Load Testing, Defect Tracking

Test Director : Software Test Management Tool

Creation of a database of manual and automated tests, building of test cycles, running tests, and report and track defects

With WinRunner, tests can be directly saved into the Test Director database

Tests can be executed in WinRunner and the overall results can be reviewed in Test Director

Load Runner : Testing tool for Client/Server Applications

Using Load Runner, you can emulate an environment in which many users (virtual users) are simultaneously engaged in a single server application

You can test an application’s performance “under load” by simultaneously activating virtual users on multiple host computers.

Summary

Advantages of Automated Testing over Manual Testing (Fast, Reliable, Repeatable, Programmable, Comprehensive, Reusable)

The WinRunner Testing Process

Creating the GUI Map,Creating Tests,Debugging Tests,Running Tests,Viewing Results, Reporting Defects

WinRunner Recording Modes (Context Sensitivity,Analog)

Recording a Test

Working with other Test Suite Tools (Test Director, Load Runner)

LAB EXERCISE

Record Login Process from Flight Reservation Sample Application in Context Sensitivity Mode

Record Flight Reservation Sample Application for Insert Order,Open Order and Fax Order

Record Burger Application for Order Entry Box

Day 2

Topic

Setting up GUI Map

Managing GUI Map

Using the Rapid Test Script Wizard

How Does WinRunner Create the Script?

How Does WinRunner Create the Script? John set_window("Login", 10); edit_set ("Name", ”John"); Recording WinRunner AUT

WinRunner adds windows and objects to the GUI Map as they are encountered by the user during recording

The GUI Map contains information that allows WinRunner TSL statements to be translated into Windows commands, and vice versa

GUI Map

How Does WinRunner Run the Script? set_window("Login", 10); edit_set ("Name", ”John"); John Playback WinRunner AUT

When WinRunner executes a TSL statement, it passes through the GUI Map before being sent to Windows

The application’s response must pass through the GUI Map also

GUI Map

Main Issues in Script Creation

Unique Identification of objects

WinRunner must uniquely identify each object in the Graphical User Interface (GUI) of the application

Naming of objects

How will WinRunner refer to GUI objects in the application? ("Press the OK button in the Open window")

How Does WinRunner Identify an Object? John ******* WinRunner uses an object’s physical attributes to identify the object Displayed label class MSW_class x y abs_x abs_y maximizable focused width height active MSW_id handle minimizable nchildren enabled TOOLKIT_class ATTRIBUTES

How Does WinRunner Uniquely Identify an Object? John ******* WR uses the minimum number of static attributes to achieve unique identification label class Class: push_button Label: “OK”

How Does WinRunner Assign Object Names? John ******* WinRunner assigns a short name to each object called the logical name Class: push_button Label: “OK” button_press (“ OK ”); edit_set (“ Name ”, “John”); edit_set (“ Password ”, “mercury”);

Into Which Field Will WinRunner Play Back? set_window("Login", 10); edit_set ("Name:", "John"); John ? ?

Scope of Identification edit_set ("Name:", "John"); John WinRunner identifies an object within the scope of its parent window (not the entire application) set_window ("Login", 10);

WinRunner Tracks AUT’s Windows and Objects With the GUI Map File

The GUI Map file contains the:

Windows of the AUT

Objects within each window

Physical attributes that create each object’s unique identification

GUI Map File Name: Physical Description: Name class: edit attached_text: "Name" WINDOW: Login Password class: edit attached_text: "Password" OK class: push_button label: "OK"

GUI Map Editor

Visual tree displays windows and objects contained in the GUI Map File

First level consists of all windows in AUT

Second level consists of objects uniquely identified within each parent window

Parent Window (logical name) Physical Description of window or object highlighted above Child Objects (logical names)

The GUI Map

Allows separation of physical attributes from test scripts

Enables WinRunner to uniquely identify objects in the AUT using physical attributes

Allows WinRunner to refer to objects in the script using an intuitive logical name

Provides the connection between logical names and physical attributes

Maintainability

If a button label changes in the application, update the button description once in the GUI map rather than in 500 tests

Readability

button_press("Insert") instead of button_press("{class: ThunderSSCommand}");

Portability

Use the same script for all platforms, with a different GUI map for each platform

Characteristics Strengths

GUI Map Translates Logical Names Into Physical Descriptions Options Class: Window Label: Window Dealer Name Class: Edit label: DealerName Address Class: Window Label: Address Login Class: Window Label: Login Automobile Purchase Form Class: Window Label: APF Customer Name Class: Edit label: CustomerName Make Class: Window Label: Make SCRIPT GUI MAP AUT set_window("Automobile Purchase Form", 10); edit_set ("Address","234 Willow Drive"); edit_set ("Customer Name", "Thomas Paine"); Logical Name Physical Description

Recording Example Application GUI Map Logical Physical { class: window, MSW_id: 3277 label: "Save As" } { class: push_button, label: "OK" } "Save As" "OK" set_window ("Save As", 1); button_press ("OK"); Test Script WinRunner

Playback Example

Save As

Application GUI Map Logical Physical { class: window, MSW_id: 3277 label: "Save As" } { class: push_button, label: "OK" } "Save As" "OK" set_window ("Save As", 1); button_press ("OK"); Test Script WinRunner

Summary

WinRunner uniquely identifies every object in the AUT by its physical description

Each object is uniquely identified within the scope of its parent window (not the entire application)

WinRunner references each object in the script using a logical name

Objects and their descriptions are stored in a GUI Map File

The GUI Map File can be viewed in the GUI Map Editor

Techniques For Managing GUI Map Files Technique 1 One GUI Map file per test Technique 2 One GUI Map file for many tests

Object and Window Properties During Recording Name: Description: Date class: edit attached_text: "Date" set_window("Automobile Purchase Form", 10); list_select_item ("Make", "BMW"); edit_set ("Year", "1973"); edit_set("Model", "2002tii"); WINDOW: Automobile Purchase Form Year class: edit attached_text: "Year" Make class: list attached_text: "Make" Model class: edit attached_text: "Model" edit_set ("Date", "12/12/03"); WinRunner stores the names and descriptions for windows and objects in a temporary GUI Map file Temporary GUI Map file Technique 1

What Happens to These Properties? Use the GUI Map Editor to save the contents of the Temporary GUI Map file to a permanent GUI Map file Technique 1 Temporary GUI Map file Name: Description: Date class: edit attached_text: "Date" WINDOW: Automobile Purchase Form Year class: edit attached_text: "Year" Make class: list attached_text: "Make" Model class: edit attached_text: "Model"

Creating a Permanent GUI Map File Car_App.gui L1 Car_App.gui Insert Test1 Test2 Testing Project Tests GUI Technique 1

Adding New Windows and Objects to a GUI Map File Invoke the GUI Map Editor 1 Technique 1

Adding New Windows and Objects to a GUI Map File Technique 1 Invoke the GUI Map Editor 1 Press the Expand Button to display Temporary and Permanent GUI Map files 2

Adding New Windows and Objects to a GUI Map File Technique 1 Invoke the GUI Map Editor 1 Move contents of Temp to Permanent by pressing Move button 3 Press the Expand Button to display Temporary and Permanent GUI Map files 2

Adding New Windows and Objects to a GUI Map File Technique 1 Save changes to permanent GUI Map file 4 Invoke the GUI Map Editor 1 Press the Expand Button to display Temporary and permanent GUI Map files 2 Move contents of Temp to permanent by pressing Move button 3

Save Project GUI Map Files Together Insert Test1 Test2 Testing Project Tests Insert.gui L1 Insert.gui GUI Test1.gui Test2.gui Technique 1

Techniques for Managing GUI Map Files Technique 1 One GUI Map file per test Technique 2 One GUI Map file for many tests

Creating a Permanent GUI Map File Technique 2 Invoke the GUI Map Editor 1

Creating a Permanent GUI Map File The cursor changes to a pointing hand Technique 2 Invoke the GUI Map Editor 1 Click the Learn Button 2

Creating a Permanent GUI Map File The cursor changes to a pointing hand Technique 2 Invoke the GUI Map Editor 1 Click the Learn Button 2 Click on the Window to be learned 3

Creating a Permanent GUI Map File The cursor changes to a pointing hand WinRunner learns all objects in window Technique 2 Invoke the GUI Map Editor 1 Click the Learn Button 2 Click on the Window to be learned 3

Creating a Permanent GUI Map File The cursor changes to a pointing hand WinRunner learns all objects in window Technique 2 Invoke the GUI Map Editor 1 Click the Learn Button 2 Click on the Window to be learned 3 Repeat for all windows in the application 4

Modify Names for Script Readability These names are unreadable. To what objects do they refer ? Technique 2

Modify Names for Script Readability Technique 2 Highlight the object whose name you want to change 1

Modify Names for Script Readability Technique 2 Highlight the object whose name you want to change 1 Click the Modify Button 2

Modify Names for Script Readability Technique 2 Highlight the object whose name you want to change 1 Change the Logical Name of the object 3 Click the Modify Button 2 Click OK 4

Modify Names for Script Readability "Name:” appears in your test script during recording instead of "ThunderRTTextBox_0" RESULT ! Technique 2 Click OK 4 Highlight the object whose name you want to change 1 Change the Logical Name of the object 3 Click the Modify Button 2

Creating a Permanent GUI Map File Car_App.gui L1 Car_App.gui Insert Test1 Test2 Testing Project Tests GUI Technique 2

Which Technique Should You Use? Technique 1 Advantages 1. Each test has GUI Map file independence 2. There is no need for a GUI Map file administrator 3. The GUI Map file is very simple to create–record and save Preferred method if the application is not intended to change during renovation Technique 2 Advantages 1. Object and window names can be very readable in the test script 2. If an object or window description changes, you only have to modify one GUI Map file–all tests will play back properly Preferred method if the application might change during renovation

Importance of the GUI Map File ? set_window("Automobile Purchase Form", 10); edit_set ("Date", "12/12/03"); list_select_item ("Make", "BMW"); edit_set ("Year", "1973"); edit_set("Model", "2002tii"); edit_set ("Purchase Price", "20000.00"); What happens when playback is attempted, and the proper GUI Map file is not loaded? Automobile Purchase Form Date

Load GUI Map File from Script GUI_load("N:\Y2K_Proj\GUI\insert.gui"); set_window("Automobile Purchase Form", 10); edit_set ("Date", "12/12/03"); list_select_item ("Make", "BMW"); edit_set ("Year", "1973"); edit_set("Model", "2002tii"); edit_set ("Purchase Price", "20000.00"); 12/12/03 BMW 1973 2002tii Insert.gui

Unload GUI Map File from Script GUI_load("N:\Y2K_Proj\GUI\insert.gui"); Insert.gui set_window("Automobile Purchase Form", 10); edit_set ("Date", "12/12/03"); list_select_item ("Make", "BMW"); edit_set ("Year", "1973"); edit_set("Model", "2002tii"); edit_set ("Purchase Price", "20000.00"); GUI_close_all( ); 12/12/03 BMW 1973 2002tii

Fixing the GUI Map File set_window("Automobile Purchase Form", 10); edit_set ("Date", "12/12/03"); list_select_item ("Make", "BMW"); edit_set ("Year", "1973"); edit_set("Model", "2002tii"); edit_set ("Purchase Price", "20000.00"); GUI Map file Name: Description: Date class: edit MSW_id: 14

Fixing the GUI Map File 2 set_window("Automobile Purchase Form", 10); edit_set ("Date", "12/12/03"); list_select_item ("Make", "BMW"); edit_set ("Year", "1973"); edit_set("Model", "2002tii"); edit_set ("Purchase Price", "20000.00"); 1 GUI Map file Name: Description: Date class: edit MSW_id: 14

Use the GUI Map Editor to Fix File *L1 Insert.gui L1 Insert.gui Active GUI file: N:\Y2K_Project\GUIinsert.gui Invoke the GUI Map Editor 1 Edit the description 3 Save the file 4 Highlight field and press Modify 2

Fixing the GUI Map File 12/12 /03 set_window("Automobile Purchase Form", 10); edit_set ("Date", "12/12/03"); list_select_item ("Make", "BMW"); edit_set ("Year", "1973"); edit_set("Model", "2002tii"); BMW 1973 2002tii ! Success WinRunner can now successfully playback the script

Custom User Toolbar

The Custom User Toolbar feature allows you to customize WinRunner’s UI to suit your testing needs

Create shortcuts to frequently used WinRunner menu commands

Paste TSL statements into your test scripts

Execute TSL statements

Add GUI Map Editor to the Custom User Toolbar An icon for each command selected is added to the User Toolbar Select Settings > Customize User Toolbar 1 In each category, select command(s) to appear in toolbar 2

Summary

Two methods to manage GUI Map files

1 GUI Map per test

if AUT is not expected to change

easiest way to create a GUI Map file

1 GUI Map for many tests

if changes to AUT are expected

most easily maintained

Use the GUI Map Editor to fix GUI Map file problems

LAB EXERCISE

Use GUI Spy to learn the objects

Record Flight Application Sample and Save the temporary GUI Map file and Load the same GUI Map file (Use function)

Create GUI Map for the same Using Learn option

Merge Login and Flight Application GUI Map file into a single one

Create a GUI Map File for Burger Application using the Learn option

Day 3

Topic

Introduction to Verification

GUI Checkpoints

Database Checkpoints

Bitmap Checkpoints

Text Checkpoints

Verification GUI Checkpoints Database Checkpoints Bitmap Checkpoints Text Checkpoints

Verifying the AUT - Manual Testing PASS ? Step Step Description Expected Result 1 Select File > New SOFTWARE REQUIREMENT SPECIFICATIONS 2.3.2 Creating a New Order Once the end user selects File > New and enters their name, the "Terms" button is automatically enabled.

Verifying the AUT - Manual Testing Step Step Description Expected Result William Frawley PASS ? 2 Enter your name The Terms button is enabled 1 Select File > New SOFTWARE REQUIREMENT SPECIFICATIONS 2.3.2 Creating a New Order Once the end user selects File > New and enters their name, the "Terms" button is automatically enabled.

Verifying the AUT - Manual Testing Step Step Description Expected Result 2 Enter your name The Terms button is enabled 1 Select File > New William Frawley PASS ? SOFTWARE REQUIREMENT SPECIFICATIONS 2.3.2 Creating a New Order Once the end user selects File > New and enters their name, the "Terms" button is automatically enabled.

Verifying the AUT - Automated Testing     William Frawley ? set_window ("Automobile Purchase Form", 8); menu_select_item ("File;New Form"); edit_set ("Customer Name", "William Frawley"); SOFTWARE REQUIREMENT SPECIFICATIONS 2.3.2 Creating a New Order Once the end user selects File > New and enters their name, the "Terms" button is automatically enabled.

What Is WinRunner Verification? Definition: Verification is the process by which WinRunner reports whether expected results are actualized by the application.

How WinRunner Verifies WinRunner compares the actual result to the stored, expected result 3 WinRunner captures an actual result during playback 2 1 WinRunner or the tester stores an expected result with the recorded test script WinRunner reports the comparison outcome as PASS or FAIL 4

How Does a Checkpoint Work? 1 2 3 4 = X ? WinRunner WinRunner WinRunner WinRunner Pass Fail Test Report Expected AUT Actual Expected AUT Actual

Process to Create Verification Run the recorded test script to verify correct execution 3 Test the checkpoint to ensure that it works for PASS and FAIL conditions 2 1 Capture or create the expected result within the recorded test script The tester creates the expected result only for text verification NOTE

Playback - Run Modes

DEBUG To check for errors in the script (Results folder: debug )

VERIFY To test the application and verify the result (Results folder: res1 (default); user can rename)

UPDATE To overwrite the expected result with a new value (Results folder: exp )

GUI Object Verification

Is the window the correct size?

Is the OK button enabled?

What is the content of the Name field?

Check the state or attributes of GUI objects:

Database Verification

Check the contents and dimensions of a database

Directly verify database-related transactions

Bitmap Image Verification

Check non-GUI object areas of the application by capturing a bitmap

Capture bitmap of window, object, or area of screen

Text Verification

Read and verify text from bitmap areas or non-GUI object based interfaces (e.g., ASCII)

Summary

Verification allows WinRunner to check the AUT's behavior

Types of verification checks

GUI objects

databases

bitmap images

text

Use GUI Object verification whenever possible, because it is the most reliable

How Does GUI Checkpoints Work ? 1 2 3 4 = X ? WinRunner WinRunner WinRunner WinRunner Pass Fail Test Report Expected Actual Expected Actual AUT AUT

Process for GUI checkpoints Test the Checkpoint to ensure that it works for ‘Pass’ & ‘Fail’ conditions 3 Create GUI checkpoint 2 1 Determine the visual cue(s) Run the recorded Test Script to verify correct execution 4

Process for GUI checkpoints 1 Determine the visual cue(s)

Which visual cues demonstrate that the AUT meets requirements

Flight Reservation Order information form

On click of Insert Order

… a visual cue is given by the application

Application returns a message Application returns a value Object changes its state GUI object example

Determine which visual cues to verify ?

Edit Field

Compare

Enabled

Focus

Range

Check Button

Enabled

Focus

Label

Pushbutton

Enabled

Focus

Label

Width

Height

Checkpoint differs depending on the object to be verified Win_check_info Window Obj_check_info Generic Object button_check_info Button(check,radio,push) list_check_info List Checkpoint function Type of Object

Process for GUI checkpoints Create GUI checkpoint 2 1 Determine the visual cue(s)

Create GUI Checkpoints

Select Checkpoint to fit the verification

State, Label Enabled, Focus Multiple properties of multiple objects Enabled, Label Multiple properties of one object Enabled One property of one object Example Type of GUI Checkpoint

Check One property of one Object

Select GUI Checkpoint for single property

set_window(“Login", 2); obj_type (“Agent Name:”,”<kTab>”); edit_set (“Password", “mercury"); edit_set (“Agent Name:", “Test");

Check One property of one Object

Select GUI Checkpoint for single property

button_check_info (“OK”,”enabled”,0);

Point to the Object

WinRunner inserts button_check_info statement into the recorded Test Script

Check Multiple properties of one Object

Select GUI Checkpoint for Object/Window

obj_check_gui ( "OK" , "list1.ckl" , "gui1" , 1 );

Point to the Object

Select Multiple properties for the objects

obj_check_gui ( "OK" , "list1.ckl" , "gui1" , 1 );

Point to the Object

Select Multiple properties for the objects

WinRunner inserts a obj_check_gui statement

Check Multiple properties of multiple Objects

Select GUI Checkpoint for Multiple Objects

Click Add and point to the object

Click Add and point to the object

Select Multiple properties for multiple objects

win_check_gui ( "Login" , "list2.ckl" , "gui2" , 1 );

Point to the Object

Select Multiple properties for multiple objects

WinRunner inserts a win_check_gui statement

Process for GUI checkpoints Test the Checkpoint to ensure that it works for ‘Pass’ & ‘Fail’ conditions 3 Create GUI checkpoint 2 1 Determine the visual cue(s)

Test the checkpoint

Checkpoint should work for both ‘Pass’ and ‘Fail’ condition

Set the object to a state that should ‘Pass’

Step through the checkpoint in Debug mode

Set the object to a state that should ‘Fail’ (Reverse the object state)

Step through the checkpoint again

Verify correct execution

Process for GUI checkpoints Test the Checkpoint to ensure that it works for ‘Pass’ & ‘Fail’ conditions 3 Create GUI checkpoint 2 1 Determine the visual cue(s) Run the recorded Test Script to verify correct execution 4

Verify correct Script Execution

After successfully testing the Checkpoints for ‘Pass’ and ‘Fail’ conditions

We are ready to run the entire Script

Script should run without error

When Script is ok, we are ready to test the application under test (AUT)

Test directory after GUI Checkpoint Testing Project Tests chklist List1.ckl exp Test2 gui1.chk Test1 Test2

Summary

GUI Checkpoint can verify

One property of one object

Multiple properties of one objects

One or more properties of several objects

Expected results are stored in exp folder

Actual results are stored in results folder

Database Checkpoint Definition: A test script checkpoint which verifies the schema table contains the expected data

Flight Database Schema Flight_Number (FK) Order_Number (PK) Orders Flight_Number (PK) Flight A Foreign Key value in a table must exist as a Primary Key value in a referenced table or be null Referential Integrity

Queries Extract Data

Select Order_Number from Orders Where Flight_Number = ‘19075’

11 Order_Number

Why use Database Checkpoints ?

Does the AUT insert , update and delete records correctly

Do the new versions of the database function properly

Does the AUT maintain referential integrity

What can you check in a Database ?

No of Columns

No of Rows

Data content of the tables

How does WinRunner Query the Data ?

WinRunner integrates with MS Query or a Data Junction

MS Query is used to create a query to extract data

The query is used by WinRunner to capture the expected and actual values from the table(s)

How Does Database Checkpoint Work ? 1 2 3 4 = X ? WinRunner WinRunner WinRunner WinRunner Pass Fail Test Report Expected Actual Expected Actual AUT AUT

Process for Database Checkpoints Test the condition to ensure that it works for Pass and Fail conditions 3 Use Database Checkpoint wizard to implement the Database Checkpoint 2 1 Record User actions to create database transaction Run the recorded scripts 4

Process for Database Checkpoints 1 Record User actions to create database transaction

Record user actions to create a Database transaction edit_set ( "Name:" , "Preeti" ); button_press ( "Insert Order" ); Preeti set_window ( "Flight Reservation" , 7 ); edit_set ( "Date of Flight:" , "09/06/02" );

Process for Database Checkpoints Use Database Checkpoint wizard to implement the database checkpoint 2 1 Record User actions to create database transaction

Use Database Checkpoint Wizard

Select Database Checkpoint for default check

Create a Query to extract data

db_check ( "list1.cdl" , "dbvf1" );

Create a Query to extract data

WinRunner inserts a db_check statement

Process for Database checkpoints Test the condition to ensure that it works for Pass and Fail conditions 3 Use Database Checkpoint wizard to implement the database checkpoint 2 1 Record User actions to create database transaction

Test the checkpoint

Set the database to a state that should ‘Pass’

Set the database to a state that should ‘Fail’ (Reverse the object state)

Process for Database checkpoints Test the Checkpoint to ensure that it works for ‘Pass’ & ‘Fail’ conditions 3 Use Database Checkpoint wizard to implement the database checkpoint 2 1 Record User actions to create database transaction Run the recorded scripts 4

Test directory after Database Checkpoint Testing Project Tests chklist list1.cdl msqr1.sql exp Test2 dbvf1 Test1 Test2

Summary

Use Database Checkpoints to verify data in the Database

Use MS Query to extract data

WinRunner uses Query to capture expected and Actual results

Always restore the database to its original state before each Test execution

Bitmap Checkpoint Definition:

Bitmap checkpoint are non–context sensitive and are dependent upon the screen resolution

Color scheme (screen resolution and no of colors)

Use Bitmap checkpoint only when verification cannot be accomplished using object or window attributes Tip

Is Bitmap Checkpoint necessary? Bitmap Checkpoint GUI Checkpoint

Used to verify non-GUI Object areas e.g. Drawing Area

When unable to use GUI Checkpoint

Useful for Graphs etc.

Most Reliable

Maintainable

Preferred method for buttons etc.

How Does Bitmap Checkpoint Work ? 1 2 3 4 = X ? WinRunner WinRunner WinRunner WinRunner Pass Fail Test Report Expected Actual Expected Actual AUT AUT

Process for Bitmap Checkpoints Test the condition to ensure that it works for Pass and Fail conditions 3 Create a Bitmap Checkpoint in the recorded Test Script 2 1 Is Bitmap verification necessary If yes verify screen area or object/window? Run the recorded scripts Differences are reported in Test Results and the difference Bitmap is found 4

Process for Bitmap Checkpoints Create a Bitmap Checkpoint in the recorded Test Script 2 1 Is Bitmap verification necessary If yes verify screen area or object/window?

Create a Bitmap Checkpoint

Create a Bitmap Checkpoint for Object/Window or a Screen Area

Point to the object

obj_check_bitmap ( "Name:" , "Img1" , 1 );

Point to the Object

WinRunner inserts a obj_check_bitmap statement

Process for Bitmap Checkpoints Test the condition to ensure that it works for Pass and Fail conditions 3 Create a Bitmap Checkpoint in the recorded Test Script 2 1 Is Bitmap verification necessary If yes verify screen area or object/window?

Test the checkpoint

Set the object to a state that should ‘Pass’

Set the object to a state that should ‘Fail’ (Reverse the object state)

Process for Bitmap Checkpoints Test the Checkpoint to ensure that it works for ‘Pass’ & ‘Fail’ conditions 3 Create a Bitmap Checkpoint in the recorded Test Script 2 1 Is Bitmap verification necessary If yes verify screen area or object/window? Run the recorded scripts Differences are reported in Test Results and the difference Bitmap is found 4

Differences are reported and the difference Bitmap is found

Expected Result

Actual Result Difference Bitmap

Summary

Use Bitmap checkpoint for non GUI objects

You can define specific area of bitmap to verify

WinRunner captures a difference bitmap when checkpoint fails

Use GUI checkpoint whenever possible

Why use a Text Checkpoint ?

Verify range of values

Calculate dynamic values

Branch a test according to the value read from the screen

Color, Font and Resolution independent

Reliable, Portable and Maintainable

Process for Text Checkpoints Insert code to compare the actual and expected value 3 Insert a function to read the actual text from the AUT during playback 2 1 Define a variable in the script and assign the expected value Insert code to report the comparison outcome to WinRunner Test Results window 4

Process for Text Checkpoints 1 Define a variable in the script and assign the expected value

Define a variable in the script and assign the expected value

for e.g. tickets_sold =“Total tickets sold is 26”

Process for Text Checkpoints Insert a function to read the actual text from the AUT during playback 2 1 Define a variable in the script and assign the expected value

Insert a function to read the actual text from the AUT during playback

There are three ways to insert functions depending on the Text type

If Text is ….

Attribute of Standard or a Custom Object Part of custom GUI object which cannot be read as an attribute Bitmap obj_get_info obj_get_text win_get_text

Process for Text Checkpoints Insert code to compare the actual and expected value 3 Insert a function to read the actual text from the AUT during playback 2 1 Define a variable in the script and assign the expected value

Insert code to compare the actual and expected value

set_window("Graph", 1); obj_get_text("GS_Drawing", text);

if (text == "Total Tickets Sold is 26" ) report_msg(“Message is correct"); else report_msg(“Message is not correct");

Process for Text Checkpoints Insert code to compare the actual and expected value 3 Insert a function to read the actual text from the AUT during playback 2 1 Define a variable in the script and assign the expected value Insert code to report the comparison outcome to WinRunner Test Results window 4

LAB EXERCISE

In the “Burger Application” check whether Medium Burger,Medium French French Fries and Apple juice are selected by using GUI checkpoints .Change the defaults and press Reset button.Ensure that Reset is functioning properly by using GUI checkpoints.

Create a Bitmap checkpoint on Order No and Graph of Flight Reservation

Create a text checkpoint on any of page and verify the results .Search for “Sample “ word in the application using text checkpoint.

Create a database checkpoint to check whether a record is inserted or not by adding checkpoint on Order No

Data Driven Tests

Data-Driven Tests

In this lesson you will learn:

What is a data-driven test

How to work with Data Tables

How to implement a data-driven test

How to import data from a database

What is a Data-Driven Test?

A test contains:

Actions: list_select_item("Fly From:","Denver");

Objects: list_select_item("Fly From:","Denver");

Data: list_select_item("Fly From:","Denver");

What if you want to use different data? San Francisco Los Angeles London

What is a Data-Driven Test?

Data-driven test:

Test is modified to read data from the Data Table

Data is entered in the Data Table

“ Denver” ); Objects

list_select_item ( "Fly From:”,

Recorded Value Actions Data Table ddt_val (table, fly_from) ); Data

What Is the Data Table? The Data Table is a spreadsheet file in WinRunner that stores the input values you will use to data-drive your test . Definition:

Advantages of a Data-Driven Test

Run the same test with different data

Expandable

Easy to maintain

Data Driving Tests Create a test 1 Modify test to read from Data Table 2 3 Move data to Data Table 1. Create test with data 2. Verify script is ready for data driving Create a test

1. Create a Test Create Test with Data invoke_application(“flight1a.exe","","C:\",SW_SHOW); set_window ("Login", 10); edit_set ("userid", "Josephine"); password_edit_set ("password", “kxpvnwoulxjuax” ); button_press ("OK"); set_window ("Flight Reservation", 10); win_check_gui("Flight Reservation", "list1.ckl", "gui1", 1); menu_select_item ("File;Exit"); Test Script

1. Create a Test Verify that Script Is Ready to Data Drive invoke_application(“flight1a.exe","","C:\",SW_SHOW); set_window ("Login", 10); edit_set ("userid", "Josephine"); password_edit_set ("password", “kxpvnwoulxjuax” ); button_press ("OK"); set_window ("Flight Reservation", 10); win_check_gui("Flight Reservation", "list1.ckl", "gui1", 1); menu_select_item ("File;Exit"); Does the script verify the expected results? Are all actions that involve inputting data recorded into the script? Are all synchronization points entered into the script? Are the initial and end conditions the same? ? Test Script

Data Driving Tests Create a test 1 Move data to Data Table 3 Modify test to read from Data Table 2 Modify test to read from Data Table 1. Run DataDriver Wizard

The DataDriver Wizard will convert your baseline script table = "default.xls" ; rc = ddt_open (table, DDT_MODE_READ); if (rc!= E_OK && rc != E_FILE_OPEN) pause ( "Cannot open table." ); ddt_get_row_count (table,table_RowCount); for (table_Row = 1 ; table_Row <= table_RowCount; table_Row ++) { ddt_set_row (table,table_Row); invoke_application ( "D:\flight1a.exe" , "" , "" ,SW_SHOW); set_window ( "Login" , 10 ); edit_set ( "Agent Name:" , ddt_val (table, "Agent_Name" )); password_edit_set ( "Password:" , ddt_val (table, "Password" )); button_press ( "OK" ); set_window ( "Flight Reservation" , 22 ); menu_select_item ( "File;Exit" ); } ddt_close (table); so that it will: 2. Modify Test to Read from Data Table What Does the DataDriver Do? Open the Data Table and check that it was successfully opened 1 invoke_application ( "D:\flight1a.exe" , "" , "" ,SW_SHOW); set_window ( "Login" , 10 ); edit_set ( "Agent Name:" , "Catherine" ); password_edit_set ( "Password:" , "kzptnyoslzjsaz" ); button_press ( "OK" ); set_window ( "Flight Reservation" , 22 ); menu_select_item ( "File;Exit" );

Open the Data Table and check that it was successfully opened 1 table = "default.xls" ; rc = ddt_open (table, DDT_MODE_READ); if (rc!= E_OK && rc != E_FILE_OPEN) pause ( "Cannot open table." ); ddt_get_row_count (table,table_RowCount); for (table_Row = 1 ; table_Row <= table_RowCount; table_Row ++) { ddt_set_row (table,table_Row); invoke_application ( "D:\flight1a.exe" , "" , "" ,SW_SHOW); set_window ( "Login" , 10 ); edit_set ( "Agent Name:" , ddt_val (table, "Agent_Name" )); password_edit_set ( "Password:" , ddt_val (table, "Password" )); button_press ( "OK" ); set_window ( "Flight Reservation" , 22 ); menu_select_item ( "File;Exit" ); } ddt_close (table); The DataDriver Wizard will convert your baseline script so that it will: 2. Modify Test to Read from Data Table What Does the DataDriver Do? Add a loop to read through all your data rows 2

table = "default.xls" ; rc = ddt_open (table, DDT_MODE_READ); if (rc!= E_OK && rc != E_FILE_OPEN) pause ( "Cannot open table." ); ddt_get_row_count (table,table_RowCount); for (table_Row = 1 ; table_Row <= table_RowCount; table_Row ++) { ddt_set_row (table,table_Row); invoke_application ( "D:\flight1a.exe" , "" , "" ,SW_SHOW); set_window ( "Login" , 10 ); edit_set ( "Agent Name:" , ddt_val (table, "Agent_Name" )); password_edit_set ( "Password:" , ddt_val (table, "Password" )); button_press ( "OK" ); set_window ( "Flight Reservation" , 22 ); menu_select_item ( "File;Exit" ); } ddt_close (table); Open the Data Table and check that it was successfully opened 1 The DataDriver Wizard will convert your baseline script so that it will: 2. Modify Test to Read from Data Table What Does the DataDriver Do? Add a loop to read through all your data rows 2 Parameterize data values so that it reads from the Data Table 3

2. Modify Test to Read from Data Table What Does the DataDriver Do? table = "default.xls" ; rc = ddt_open (table, DDT_MODE_READ); if (rc!= E_OK && rc != E_FILE_OPEN) pause ( "Cannot open table." ); ddt_get_row_count (table,table_RowCount); for (table_Row = 1 ; table_Row <= table_RowCount; table_Row ++) { ddt_set_row (table,table_Row); invoke_application ( "D:\flight1a.exe" , "" , "" ,SW_SHOW); set_window ( "Login" , 10 ); edit_set ( "Agent Name:" , ddt_val (table, "Agent_Name" )); password_edit_set ( "Password:" , ddt_val (table, "Password" )); button_press ( "OK" ); set_window ( "Flight Reservation" , 22 ); menu_select_item ( "File;Exit" ); } ddt_close (table); Open the Data Table and check that it was successfully opened 1 The DataDriver Wizard will convert your baseline script so that it will: Add a loop to read through all your data rows 2 Parameterize data values so that it reads from the Data Table 3 Close the Data Table 4

2. Modify Test to Read from Data Table Running the DataDriver Wizard invoke_application(“flight1a.exe","","C:\",SW_SHOW); set_window ("Login", 10); edit_set ("userid", ”Catherine"); password_edit_set ("password", “kxpvnwoulxjuax” ); button_press ("OK"); set_window ("Flight Reservation", 10); win_check_gui("Flight Reservation", "list1.ckl", "gui1", 1); menu_select_item ("File;Exit"); 1. Highlight area you want to be data driven. 2. Start the DataDriver Wizard. invoke_application(“flight1a.exe","","C:\",SW_SHOW); set_window ("Login", 10); edit_set ("userid", ”Catherine"); password_edit_set ("password", “kxpvnwoulxjuax” ); button_press ("OK"); set_window ("Flight Reservation", 10); win_check_gui("Flight Reservation", "list1.ckl", "gui1", 1); menu_select_item ("File;Exit"); 1 2

2. Modify Test to Read from Data Table Running the DataDriver Wizard Final Result table = " default.xls "; rc = ddt_open( table , DDT_MODE_READ); if (rc!= E_OK && rc != E_FILE_OPEN) pause("Cannot open table."); ddt_get_row_count( table , table_RowCount); for(table_Row = 1; table_Row <= table_RowCount; table_Row ++) { ddt_set_row( table ,table_Row); invoke_application("D:\flight1a.exe","","",SW_SHOW); set_window ("Login", 10); edit_set ("Agent Name:",ddt_val( table ,"Agent_Name")); password_edit_set("Password:",ddt_val( table ,"Password")); button_press ("OK"); set_window ("Flight Reservation", 22); menu_select_item ("File;Exit"); } ddt_close( table );

2. Modify Test to Read from Data Table Running the DataDriver Wizard Where does the Data Table reside? <test name> default.xls

2. Modify Test to Read from Data Table Running the DataDriver Wizard How do you populate the Data Table?

If you want to import data from a database, do it now, using the Wizard

Other methods will be discussed in the next section, “Move Data”

3. Move Data to Data Table Importing Data From Database to Data Table Database

2. Modify Test to Read from Data Table Running the DataDriver Wizard edit_set ("Agent Name:", “Catherine”); ? Final Result edit_set(“Agent Name:”, ddt_val(table,”Agent_Name”) );

2. Modify Test to Read from Data Table Running the DataDriver Wizard

Data Driving Tests Create a test 1 2 3 Move data to Data Table Modify test to read from Data Table

3. Move Data to Data Table How Is Data Moved to Data Table?

Import, using DataDriver Wizard (covered in previous section)

Manually

Dynamically, during run time

3. Move Data to Data Table Insert Data Manually Open the Data Table 1 Enter Data you want to test 2 Close Data Table and save script 3

3. Move Data to Data Table Add Data Dynamically During Run Create Invoice Test 1 mer InvoiceNum 3421 yelet phine Data Table 3423 3423 3423 . . . . . . ddt_set_val(... Update Invoice Test 2 . . . . . . edit_set(...,ddt_val ...

3. Move Data to Data Table Add Data Dynamically During Run Add column to Data Table for data to be added 1

3. Move Data to Data Table Add Data Dynamically During Run table = "default.xls"; rc = ddt_open(table, DDT_MODE_READ); if (rc!= E_OK && rc != E_FILE_OPEN) pause("Cannot open table."); ddt_get_row_count(table,table_RowCount); for(table_Row = 1; table_Row <= table_RowCount; table_Row ++) { ddt_set_row(table,table_Row); set_window ("Automobile Purchase Form", 2); edit_set ("Customer Name",ddt_val(table,"Customer_Name")); edit_set("Address:",ddt_val(table,"Address")); edit_set ("License",ddt_val(table,"License")); obj_mouse_click ("Method of Payment", 23, 13, LEFT); button_set (ddt_val(table,"Cash"), ON); list_select_item ("Make",ddt_val(table,"Make")); # Item Number 0; edit_set ("Model",ddt_val(table,"Model")); button_press ("Insert Sale"); edit_wait_info("StatusBar","value","New Purchase Completed Successfully...",10); } ddt_close(table); Add column to Data Table for data to be added 1 ddt_set_val ( table , “ ”, InvoiceNumber ); obj_get_info ("Invoice No:","label", InvoiceNumber ); ddt_save ( table ); Modify the script so that it: 2 captures the data and saves it to a variable a sets the value in the Data Table b saves changes to the Data Table c Data Table InvoiceNo

Summary

Create a “template” test with single set of data

Modify test to read data from table

run the Data Driver Wizard

Move data to Data Table

import data from a database

edit Data Table directly

add data to Data Table during run-time

Exercise

Create a Data Driven test on Login and Password and Error Messages that it can generate.

Create Data Driven test on Customer Name field.

Lesson Objectives

In this section, we will learn

the importance of synchronization for successful test playback

how to select the appropriate synchronization type for your script

how to insert synchronization into a test script

How Do Client-Server Applications Behave? Single User Database server Server response time:

How Do Client-Server Applications Behave? Several Users Database server Server response time:

How Do Client-Server Applications Behave? Many Users Database server Server response time:

How Do Client-Server Applications Behave? Example Response Times RESPONSE TIME Several users 0.61 Many users 1.00 Single user 0.33

Complete the Business Process Manually Database 07/07/01 Los Angeles Denver Cash Enter 07/07/01 on Date field Select LA from Fly From field Select Denver from Fly To field Enter Cash as Method of Payment Press Flights button Example steps

Complete the Business Process Manually Database Enter 07/07/01 on Date field Select LA from Fly From field Select Denver from Fly To field Enter Cash as Method of Payment Press Flights button Select a flight Example steps

Complete the Business Process Manually Database 07/07/01 Los Angeles Denver Cash Errol Flynn Enter Customer Name Insert Order Wait for response before continuing Enter 07/07/01 on Date field Select LA from Fly From field Select Denver from Fly To field Enter Cash as Method of Payment Press Flights button Select a flight 7328 Close application Example steps

Manual Steps Recorded in the Test Script edit_set ("Date","070701"); list_select_item ( "Fly From:", "Los Angeles" ); list_select_item ("Fly To:", "Denver"); list_select_item ("Payment:", "Cash" ); button_press ( "Flights" ); button_press ( "Insert Order" ); ??? Enter 07/07/01 on Date field Select LA from Fly From field Select Denver from Fly To field Enter Cash as Method of Payment Press Flights button Enter Customer Name Insert Order Wait for response before continuing Select a flight win_close ( "Flight Reservation" ); Close the application set_window ( "Flights Table" , 4); button_press ( "OK" ); Example steps edit_set ( "Customer Name:" , "Errol Flynn" ); set_window ( "Flight Reservation" , 10);

Why Not Insert a Wait Statement? button_press ( "Insert Order" ); win_close ( "Flight Reservation" ); wait ( ); 10 50 users 5.1 seconds 500 users 9.5 seconds 1 user 3.7 seconds AVERAGE RESPONSE TIMES

Why Not Insert a Wait Statement? AUT 11.3 seconds RUN #1 Wait (10); button_press ( "Insert Order" ); win_close ( "Flight Reservation" ); wait ( ); 10 button_press ( "Insert Order" ); win_close ( "Flight Reservation" ); wait ( ); 15 PROBLEM: Test run failed because wait didn't last long enough SOLUTION: Add 50% to wait time as safety cushion

Why Not Insert a Wait Statement? AUT 5.5 seconds RUN #2 Wait (15); 15 seconds button_press ( "Insert Order" ); win_close ( "Flight Reservation" ); wait ( ); 15 PROBLEM: Most of the wait time was unnecessary SOLUTION: Don't use a wait statement – use something that will continue as soon a s the AUT is finished. But what will do that? button_press ( "Insert Order" ); win_close ( "Flight Reservation" ); ???

What Is a Synchronization Point? A synchronization point is a line in the test script that instructs WinRunner to wait for a certain response from the application during playback, just as a real user would. Definition:

ADD SYNCHRONIZATION POINTS Introduction to Synchronization Add Synchronization Points Record user actions in script 1 Synchronize script to application under test 2 Add verification statements to check AUT 3 Run test or suite of tests 4

Process to Add Synchronization Points Add Synchronization Points Establish visual cues to synchronize 1 Determine type of synchronization point 2 Add synchronization point to test script 3 Play back revised script 4

Establish Visual Cue to Synchronize Examples 1 Wait for a bitmap to refresh BITMAP Wait for a window WINDOW Wait for an object state OBJECT STATE

Methods of Synchronization obj_wait_info ("Bar","label", "Insert Done...", 20); Wait for an object state/property value obj_wait_bitmap ("Window", "Img1", 10, 209, 170, 81, 20 ); Wait for a bitmap set_window ("Flight Reservation", 20); Wait for a window

Determine Type of Synchronization (Waiting for a Window) 2 Window name Time set_window ("Flight Reservation", 20); Wait for main window to appear after login

Properties of Standard GUI Objects (Examples) Boolean Values 0 = False 1 = True State 3 State 2 State 1 class: push_button, focused: 1, label: "Insert Order", enabled: 1 class: push_button, focused: 0, label: "Insert Order", enabled: 1 class: push_button, focused: 0, label: "Insert Order", enabled: 0

Properties of Standard GUI Objects (Examples) Boolean Values 0 = False 1 = True State 3 State 2 State 1 class: list, focused: 1, value: "Paris" class: list, focused: 0, value: "Los Angeles" class: list, focused: 0, value: "" class: push_button, focused: 1, label: "Insert Order", enabled: 1 class: push_button, focused: 0, label: "Insert Order", enabled: 1 class: push_button, focused: 0, label: "Insert Order", enabled: 0

Properties of Standard GUI Objects (Examples) Boolean Values 0 = False 1 = True State 3 State 2 State 1 class: list, focused: 1, value: "Paris" class: list, focused: 0, value: "Los Angeles" class: list, focused: 0, value: "" class: push_button, focused: 1, label: "Insert Order", enabled: 1 class: push_button, focused: 0, label: "Insert Order", enabled: 1 class: push_button, focused: 0, label: "Insert Order", enabled: 0 class: radio_button, focused: 1, value: 1 class: radio_button, focused: 0, value: 1 class: radio_button, focused: 0, value: 0

Determine Type of Synchronization (Change in Object Property/State) 2 obj_wait_info ("Bar","label", "Insert Done...", 20); Object name Object property Synchronize with a progress bar message

Determine Type of Synchronization (Change in Object Property/State) 2 obj_wait_info ("Bar","label", "Insert Done...", 20); value Time Synchronize with a progress bar message

Determine Type of Synchronization (Waiting for a Bitmap) 2 obj_wait_bitmap ("Window", "Img1", 10, 209, 170, 81, 20 ); Object name Bitmap name Sync with browser loading a bitmap

Determine Type of Synchronization (Waiting for a Bitmap) 2 obj_wait_bitmap ("Window", "Img1", 10, 209, 170, 81, 20 ); Time x , y Sync with browser loading a bitmap

Determine Type of Synchronization (Waiting for a Bitmap) 2 obj_wait_bitmap ("Window", "Img1", 10, 209, 170, 81, 20 ); width height Img1.bmp Bitmap File Location: Test_name exp Test_name Sync with browser loading a bitmap

How Long Does It Wait? "OK" "Error" TIME PARAMETER Global timeout setting Global timeout interval GLOBAL + Test run 1 TOTAL = Maximum total timeout Synchronization statement timeout parameter Script continues Script continues Test run 2

Add Synchronization to Test Script Wait for a Window 3 # Login set_window ( "Login" ,4); edit_set ( "Agent Name:", "mercury" ); password_edit_set ( "Password:","kjzisllz" ); button_press ( "OK" ); # Flight Reservation set_window ( "Flight Reservation" , 25 ); Locate the TSL statement that points to the determined visual cue 1

Add Synchronization to Test Script Wait for a Window # Login set_window ( "Login" ,4); edit_set ( "Agent Name:", "mercury" ); password_edit_set ( "Password:","kjzisllz" ); button_press ( "OK" ); # Flight Reservation set_window ( "Flight Reservation" , 25 ); 3 Recorded time parameter reflects delay during script recording session 60 Locate the TSL statement that points to the determined visual cue 1 Modify timeout parameter to allow ample time for window to appear 2

Add Synchronization to Test Script Wait for an Object State/Property Value list_select_item ( "Fly From:","Denver" ); list_select_item ( "Fly To:","San Francisco" ); # Flights Table set_window ( "Flights Table" ,2); list_activate_item ( "Flight", "2452..." ); # Flight Reservation set_window ( "Flight Reservation" ,3); edit_set ( "Customer Name:","Bob Smith" ); button_press ( "Insert Order" ); 3 Locate the line in the script to insert the synchronization point 1

Add Synchronization to Test Script Wait for an Object State/Property Value list_select_item ( "Fly From:","Denver" ); list_select_item ( "Fly To:","San Francisco" ); # Flights Table set_window ( "Flights Table" ,2); list_activate_item ( "Flight", "2452..." ); # Flight Reservation set_window ( "Flight Reservation" ,3); edit_set ( "Customer Name:","Bob Smith" ); button_press ( "Insert Order" ); 3 Locate the line in the script to insert the synchronization point 1 Select Create > Synchronization Point/For Object/Window Property 2

Add Synchronization to Test Script Wait for an Object State/Property Value list_select_item ( "Fly From:","Denver" ); list_select_item ( "Fly To:","San Francisco" ); # Flights Table set_window ( "Flights Table" ,2); list_activate_item ( "Flight", "2452..." ); # Flight Reservation set_window ( "Flight Reservation" ,3); edit_set ( "Customer Name:","Bob Smith" ); button_press ( "Insert Order" ); 3 Using the Hand pointer, click on the object to synchronize 3 Locate the line in the script to insert the synchronization point 1 Select Create > Synchronization Point/For Object/Window Property 2

Add Synchronization to Test Script Wait for an Object State/Property Value list_select_item ( "Fly From:","Denver" ); list_select_item ( "Fly To:","San Francisco" ); # Flights Table set_window ( "Flights Table" ,2); list_activate_item ( "Flight", "2452..." ); # Flight Reservation set_window ( "Flight Reservation" ,3); edit_set ( "Customer Name:","Bob Smith" ); button_press ( "Insert Order" ); 3 "Progress Bar" Select the object attribute that will contain the value of the visual cue 4 Using the Hand pointer, click on the object to synchronize 3 Locate the line in the script to insert the synchronization point 1 Select Create > Synchronization Point/For Object/Window Property 2

Add Synchronization to Test Script Wait for an Object State/Property Value list_select_item ( "Fly From:","Denver" ); list_select_item ( "Fly To:","San Francisco" ); # Flights Table set_window ( "Flights Table" ,2); list_activate_item ( "Flight", "2452..." ); # Flight Reservation set_window ( "Flight Reservation" ,3); edit_set ( "Customer Name:","Bob Smith" ); button_press ( "Insert Order" ); 3 obj_wait_info ( "Progress Bar" , "label" , "Insert Done…”, 10); "Progress Bar" Click the Paste button in Wait for object window 5 Select the object attribute that will contain the value of the visual cue 4 Using the Hand pointer, click on the object to synchronize 3 Locate the line in the script to insert the synchronization point 1 Select Create > Synchronization Point/For Object/Window Property 2

Add Synchronization to Test Script Wait for a Bitmap Area 3 # Mercury Homepage set_window ( "Mercury Homepage" , 5 ); edit_set ( "Address", "http://www.merc-int.com” ); obj_mouse_click ( "mpage", "Img2" , 471, 328 ); Locate the line in the script to insert the synchronization point 1

Add Synchronization to Test Script Wait for a Bitmap Area # Mercury Homepage set_window ( "Mercury Homepage" , 5 ); edit_set ( "Address", "http://www.merc-int.com” ); obj_mouse_click ( "mpage", "Img2" , 471, 328 ); 3 Select Create > Synchronization Point > For Screen Area Bitmap 2 Locate the line in the script to insert the synchronization point 1

Add Synchronization to Test Script Wait for a Bitmap Area 3 # Mercury Homepage set_window ( "Mercury Homepage" , 5 ); edit_set ( "Address", "http://www.merc-int.com” ); obj_mouse_click ( "mpage", "Img2" , 471, 328 ); Click left mouse button and drag pointer to select area; press right button to complete selection 3 Select Create > Synchronization Point > For Screen Area Bitmap 2 Locate the line in the script to insert the synchronization point 1

Add Synchronization to Test Script Wait for a Bitmap Area 3 # Mercury Homepage set_window ( "Mercury Homepage" , 5 ); edit_set ( "Address", "http://www.merc-int.com” ); obj_wait_bitmap ( "mpage","Img2" ,6,7,8,101,114); obj_mouse_click ( "mpage", "Img2" , 471, 328 ); TSL statement appears in script 4 Locate the line in the script to insert the synchronization point 1 Click left mouse button and drag pointer to select area; press right button to complete selection 3 Select Create > Synchronization Point > For Screen Area Bitmap 2

Other Object State Synchronization Statements

button_wait_info

edit_wait_info

list_wait_info

menu_wait_info

obj_wait_info

scroll_wait_info

spin_wait_info

static_wait_info

statusbar_wait_info

tab_wait_info

Play Back Revised Script 4 edit_set ("Date","070703"); list_select_item ("Fly From:", "Los Angeles"); button_press ( "Flights" ); set_window ("Flights Table", 4); list_activate_item ("Flight", . . .) edit_set ( "Customer Name:", "Errol Flynn" ); button_press ( "Insert Order" ); obj_wait_info ( "ProgressBar","label", "Insert Done..." ,10); 07/07/03 Los Angeles Denver Cash edit_set ( "Date","070703" ); list_select_item ( "Fly From:", "Los Angeles" ); list_select_item ( "Fly To:", "Denver" ); list_select_item ( "Payment:", "Cash" ); set_window ( "Flights Table" , 4); list_activate_item ( "Flight" , . . .);

Play Back Revised Script 4 07/07/03 Los Angeles Denver Cash edit_set ("Date","070703"); list_select_item ("Fly From:", "Los Angeles"); list_select_item ("Payment:", "Cash"); button_press ( "Flights" ); edit_set ( "Customer Name:" , "Errol Flynn" ); button_press ( "Insert Order" ); set_window ("Flights Table", 4); list_activate_item ("Flight", . . .) obj_wait_info ( "ProgressBar","label", "Insert Done..." ,10); 07/07/03 edit_set ( "Date","070703" ); list_select_item ( "Fly From:", "Los Angeles" ); list_select_item ( "Fly To:", "Denver" ); list_select_item ( "Payment:", "Cash" ); set_window ( "Flights Table" , 4); list_activate_item ( "Flight" , . . .);

Play Back Revised Script 4 edit_set ( "Date","070703" ); list_select_item ( "Fly From:", "Los Angeles" ); list_select_item ( "Fly To:", "Denver" ); list_select_item ( "Payment:", "Cash" ); button_press ( "Flights" ); edit_set ( "Customer Name:", "Errol Flynn" ); button_press ( "Insert Order" ); obj_wait_info( "ProgressBar","label", "Insert Done..." ,10); set_window ( "Flights Table" , 4); list_activate_item ( "Flight" , . . .); . . . Errol Flynn 07/07/03 101

Summary

The AUT's performance may slow down as the number of users increases

Synchronization points allow WinRunner to wait for the AUT, just like a real user

Synchronization Points wait for

windows or bitmaps to appear

objects to change state

Maximum wait time for a Synchronization Point is the time parameter + global timeout

LAB EXERCISE

Create Bitmap Synchronization for Insert Order Image

Add Synchronization points to all INSERT,DELETE operations

Enhancing Your Test Using TSL Test Script Language

Enhancing Your Test Using TSL

In this lesson you will learn:

How TSL can enhance test scripts:

maintainability

readability

reliability

portability

Some important TSL functions

How to insert TSL statements into your script using the Function Generator

What is TSL ?

It is a C-like language

flow control (for, while, if / else…, switch)

case sensitive

operators (arithmetic, relational…)

input/output

It is a Basic-like language

constants, variables, arrays

It is interpreted for easy debugging

It has built-in Testing Functions

recorded

programmed

Variables and Constants

Use variables and constants to:

remove hard-coded data for maintainability, readability

store data (i.e., input/output data, error codes)

create data driven tests

Variables do not have to be declared

they can always contain strings or numbers

Variables and constants can be of type public or static

public: available to all tests and function libraries

static: available to only the script in which it is declared

Variables and Constants Variable and Constant Names: - letters, numbers, underscore - first character must be a letter or an underscore - case sensitive # Constant declarations public const GUI_FILE_PATH = “c:\tests\guifiles\”; public const AUT_PATH = “c:\app\bin\”; public const E_MY_ERROR_CODE = -12345; # Variable declarations static lineCounter ; public flightVersion = “Flight1a.exe”; Test Script 1 Examples GUI_load ( GUI_FILE_PATH & “myFile.gui”); invoke_application ( AUT_PATH & flightVersion , ““, AUT_PATH , SW_SHOW); ... rc = my_function (); if (rc == E_MY_ERROR_CODE ) ... Test Script 2

Variables and Constants Strings and Numbers number1 = "4" ; number2 = 3 ; value = number1 * number2; value contains 12 cost = "10 Dollars" ; amount = “The price is “ & cost + 5 ; amount contains “The price is 15” value_a = "3.3" ; value_b = "2,5" ; result_a = value_a * 2 ; result_b = value_b * 4 ; result_a contains 6.6 result_b contains 8 Sample 1 Sample 2 Sample 3 WinRunner can convert strings to numbers and vice versa! If a string is converted to a number, WinRunner cuts off all following non-numeric characters!

Variables and Constants Special Characters in Strings

The backslash is used to start an escape-sequence, (a special character)

Tab

Return, Newline

” Quotes

To Insert a backslash into a string use a double backslash

\ Backslash

value = "This is a "String" with very special character" ; pause ( value );

Arrays

Use arrays when you need to store many data values using one data structure

allow for easy access to large sets of data

allow for storing sets of data

Array size can be dynamically increased

test script expandability

Each array element can be indexed by a user-defined string (associative arrays)

Multi-dimensional arrays are supported

Arrays Simple Array fltclass[ 1 ]= "First" ; fltclass[ 2 ]= "Business" ; fltclass[ 3 ]= "Economy" ; # Data Window set_window ( "Data Window" , 1 ); edit_get_text ( "Class Number:" , class ); # Flight Reservation set_window ( "Flight Reservation" , 1 ); button_set ( fltclass[class] , ON ); Sample

Arrays Associative Array userdata[ "name" ]= "John Smith" ; userdata[ "address" ]= "1234 Main Street" ; userdata[ "zip" ]= 98711 ; userdata[ "city" ]= "Hometown " ; # Customer Information Window set_window ( ”Customer Information Window" , 1 ); edit_set ( "Name:" , userdata[ "name" ] ); edit_set ( "Address:" , userdata[ "address" ] ); edit_set ( "City:" , userdata[ "zip" ] & ", " & userdata[ "city" ] ); Sample

Arrays Multi-dimensional Arrays flightinfo[ 1 , "Date” ] = "07/22/99" ; flightinfo[ 1 , "FlyFrom” ] = "Los Angeles" ; flightinfo[ 1 , "FlyTo” ] = "Denver" ; flightinfo[ 1 , "Flight No” ] = "4300" ; flightinfo[ 2 , "Flight No” ] = "1234" ; flightinfo[ 3 , "Flight No” ] = "9999" ; Example: Multi-dimensional Array Date Fly From Fly To Flight No 1 2 3 07/22/99 09/28/01 12/26/02 Los Angeles Seattle Dallas Detroit Portland Denver 4300 1234 9999 Multi-dimensional Arrays; Data in table format

Flow Control

Add flow control to increase the test script’s reliability and maintainability

make decisions in a test script

handle predictable AUT behavior

iterate repeated user actions

handle multiple window paths in AUT

create a data driven test

Flow control constructs:

conditional

looping

flow modification

Flow Control Conditional Decision Making set_window (“Flight Reservation”); obj_get_info (“Order No:”, “value”, OrderNo); if ( OrderNo == “ ” ) report_msg (“No order number.”); else button_press (“Update Order”); set_window (“Flight Reservation”); obj_get_info (“Order No:”, “value”, OrderNo); if ( OrderNo == “ ” ) { report_msg (“No order number.”); } else { button_press (“Update Order”); } win_get_text(”Flight Info”, version, 42, 68, 159, 89); if ( version != “Version 1.0” ) { report_msg (“Wrong Version!”); texit; } Example 2 Best practice: always set curly brackets Example 1

Flow Control switch Statement set_window ("Fax Order"); edit_get_text ("Class:", class); switch (class) { case "Economy": result = PASS; message="Correct class: Economy"; break; case "Business": result = FAIL; message="Wrong class: Business"; break; case "First": result = FAIL; message="Wrong class: First"; break; } tl_step (“Class of Service”, result, message); Example

Flow Control for Loop # Looping for stress testing for (i=0; i<1000; i++) { set_window (“Flight Reservation”); menu_select_item ("File;Fax Order..."); set_window ("Fax Order"); edit_set ("Fax Number:", “4085551212”); button_press (”Send"); set_window (“Flight Reservation”); obj_wait_info (“StatusBar”, “label”, “Fax Sent”, 50); } Example

Flow Control while Loop file= "c:\data\flight_orders.txt"; file_open( file, FO_MODE_READ ); while ( file_getline( file, line ) == E_OK ) { ord_num= substr( line, 0, 5 ); open_order( ord_num ); report_msg( "Opened Order " & ord_num ); } file_close( file ); The statements in this while loop will not be executed if the condition is not TRUE (if the file cannot be opened) Example

Flow Control do while Loop # Flight Reservation set_window ( "Flight Reservation", 2 ); edit_set ( "Name:", "" ); new_len=0; do { old_len= new_len; edit_type( "Name:", "123" ); edit_get_info( "Name:", "value", value ); new_len= length( value ); } while( old_len < new_len ); report_msg( "Max Name length ” & new_len & " characters" ); The statements in this while loop are executed at least once. Example

Operators

Use operators to create expressions by combining

variables and constants

Arithmetic ( + - * / % ++ -- )

Assignment ( = += -= *= /= %= ^= )

Concatenation ( & )

Conditional ( ? )

Logical ( && || ! )

Relational ( > >= < <= == != )

Operators Arithmetic/Relational edit_get_text ("Tickets", tickets); edit_get_text ("Price", price); edit_get_text ("Total", total); if ( tickets * price == total ) tl_step (“Total”, PASS, “Correct Total”); else { tl_step (“Total”, FAIL, "Wrong Total"); report_msg(“Expected Value: ” & tickets * price); report_msg(“Actual Value: ” & total ); } Best Practice: For complicated calculations, check values in the AUT against pre-calculated values in a data table or data file Example

Operators Logical Operators # Value is greater than 50 AND less than 100 if ( value > 50 && value <100 ) tl_step (“Value tested”, PASS, “Correct Value”); Logical AND # Value equals Saturday OR value equals Sunday if ( value== “Saturday” || value== “Sunday” ) tl_step (“Value tested”, PASS, “ it’s Weekend !”); Logical OR # Value is equal to or greater than 1 AND less than or equal to 10 # AND value IS NOT 5 if ( value >=1 && value <=10 && value != 5 ) tl_step (“Value tested ”, PASS, “is between 1-10 and not 5”); Combination

TSL Testing Functions

TSL contains many non-recorded testing functions to enhance your tests

arithmetic, string

Data Table (discussed in a later lesson)

Test Report, file, query functions

synchronization

system

Finding out about functions

Function Generator

on-line help

TSL Reference manual

WinRunner Books Online

TSL Testing Functions

Arithmetic

exp

int

Input/Output

tl_step

file_getline

file_printf

Query GUI Objects

edit_get_text

obj_get_info

win_exists

String/File

substr

file_compare

Synchronization

list_wait_info

obj_wait_info

System

invoke_application

dos_system

get_time

Examples

Important TSL Functions Invoking an Application

Description: Invokes a Windows application from within a test script

Format: invoke_application (file, option, working_dir, show);

app_path= “c:\mercury\winrunner\samples”; invoke_application (app_path & “\flight1a.exe”,“”, app_path, SW_SHOW); Example

Important TSL Functions Checking for a Window

Description: This statement can be used to verify if an error message appears, the application is started, or a specific window appears on the screen.

Format: win_exists( window, [time] );

If ( win_exists ( “Flight Message” ) == E_OK ) { set_window( “Flight Message”, 2 ); button_press( “OK” ); } Example

Important TSL String Functions Splitting a String

Description: This statement can be used to split a long string into smaller parts, at every appearance of a given Separator.

Format: split(String, Array, Field Separator);

set_window("Flights Table", 1); list_get_item("Flight",num, flight); split ( flight, values, " "); if( values[1] == flight_num ) { Example

Important TSL Functions Accessing DOS

Description: Executes a DOS command from within a test (equivalent to executing a command from a DOS window)

Format: dos_system (expression);

dos_system ( "del c:\demo.tmp” ); Example

Important TSL Functions Input/Output

Read input from the WinRunner Data Table

discussed in a later lesson

Send output from test:

to the report

to TestDirector

Description: Use tl_step function to report status of a checkpoint

divides test into steps & sends a message on success / failure

affects test status (pass / fail)

makes analysis of test script execution easier

Format: tl_step (step_name, status, description);

Output to Test Report & TestDirector win_get_text ("File Name", text, 247, 309, 427, 329); if (text == "letter.doc") tl_step (“Verify Text”, PASS , “Correct text”); else tl_step (“Verify Text”, FAIL , “Wrong text: ” & text ); Example

Output to Report report_msg Statement

Description: - Send information about the test execution to the Test Report - Does not affect test status.

Format: report_msg (string);

edit_get_text ("File Name", val ); if (val != "letter.doc") { report_msg ("Error: Illegal file name: ” & val & “ Test Aborted"); } Example

Functions arranged in categories

Accessing Functions The Function Generator

Expand form to fill in argument values

Paste into script (or execute)

Point and click programming

Accessing Functions The Editor # Automobile Purchase Form set_window ( "Automobile Purchase Form" , 10); edit_set ( "Customer Name" , "Thomas Paine" ); edit_ edit_set

When you type an underscore, a list with functions will appear

Type ESC to hide the function list

Continue typing to pre-select other functions

TAB, ENTER or SPACE selects the actual function

Accessing Functions The Editor # Automobile Purchase Form set_window ( "Automobile Purchase Form" , 10); edit_set ( "Customer Name" , "Thomas Paine" ); edit_set edit_set ( edit_set ( ”Password”, “Mercury”

When you type an open bracket a ToolTip with the parameters will appear

edit_set (Edit Object, New String) edit_set ( ”Password”, “Mercury” );

Using Return Codes

Each TSL Function has a return code

numeric

general TSL error codes (E_OK, E_NOT_FOUND)

Enhance the readability of your test scripts

if (win_exists ("Flight Reservation Message") == E_OK ) {

set_window ("Flight Reservation Message");

button_press ("No");

}

rc = set_window (“Flight Reservation”, 10);

if ( rc != E_OK) {

report_msg (“Flight application did not invoke properly.”);

texit (-1); # Aborting test

}

Example 2 Example 1

Debugging Tests

Step, Step Into

Breakpoint

Watch Variables

pause Statement

Debugging Tests pause Statement

Halts execution of test script and pops up a message box

Ensures that variables and arrays contain the correct data

Capital = "Sacramento"; pause ("The capital of California is " & Capital);

Comments

WinRunner ignores anything after a “#” as a comment

Thoroughly comment test scripts for readability and maintainability

Helps other test developers analyze and edit test scripts

################################################################## # Test Name: Verify Login # # Test Developer: John Doe # # Purpose: This test verifies that the login procedure… # # Date: 12.12.97 # # Date of Last Revision: 2.14.98 # ################################################################## # Performing a login to AUT set_window (“Login”); edit_set (“Login Name”, name); # name stores the actual login name Example You can insert comments either during recording or after recording

Creating a Startup Script

A startup script can contain anything you want executed each time you start WinRunner

When working within a team you can use the same startup script to ensure everyone’s environment is similar

Set the location of your Startup script in WinRunner’s General Options

Use a startup script to:

Load your GUI map

Declare constants and variables

Load your Function Libraries

Customize your Function Generator

Configure WinRunner’s view of objects

Creating a Startup Script ############################################ # TestSuite Training Init Test # ############################################ # Loading the prepared GUI file GUI_load ( getvar ( "testname" )& "\flight60.gui" ); # Configure the MS Mask object to map to edit objec # Data of Flight recording depends on this set_class_map ( "MSMaskWndClass" , "edit" ); set_record_attr ( "MSMaskWndClass" , "class attached_t set_record_method ( "MSMaskWndClass" , RM_RECORD); # Configure the status bar in the GUI Map set_class_map ( "AfxWnd40" , "object" ); set_record_attr ( "AfxWnd40" , "class regexp_MSW_class S:TestProjectInitScript WinRunner - [InitScript] Create a startup script in WinRunner. 1 Open the General Options window and click the Environment tab. 2 Enter the path where you saved your startup script in the Startup test box. 3

Summary