Dr.SNS RAJALAKSHMI COLLEGE OF ARTS AND SCIENCE.

(AUTONOMOUS)

Re-Accredited With “A” Grade by NAAC

(Affiliated to Bharathiar University)
Coimbatore-641049

DEPARTMENT OF COMPUTER SCIENCE

III B.Sc (CS) A

Certified that this is the bonafide record work done by

NAME: ………………………………………………..

REG NO: ……………………………………………..

BATCH: 2016 - 2019

16UCS557: SOFTWARE TESTING

SIGNATURE OF HOD STAFF INCHARGE

Submitted for B.Sc Degree Sixth Semester

Practical Examination held on……….....

INTERNAL EXAMINER EXTERNAL EXAMINER

 CONTENTS

S.NO DATE TITLE OF EXPERIMENT PAGE NO SIGNATURE

1 Check the properties of the GUI

objects using GUI spy in winrunner
2 To create rapid test script using rapid
test script wizard
3 To record the operations which are
performed on an application and to run
the test again using winrunner
4 To check the text in an application
using winrunner
5 To check the bitmap images in a
project and to verify that both the
image are same
6 To test multiple application multiple
times with the help of batch mode
testing
7 To test synchronize tests for the
application

2
 Software Required: WINRUNNER
Win Runner
WinRunner, Mercury Interactive’s enterprise functional testing tool. It is used to quickly create
and run sophisticated automated tests on your application. Winrunner helps you automate the
testing process, from test development to execution. You create adaptable and reusable test
scripts that challenge the functionality of your application. Prior to a software release, you can
run these tests in a single overnight run- enabling you to detect and ensure superior software
quality.
What’s New in WinRunner 7.5?
Automatic Recovery
The Recovery Manager provides an easy-to-use wizard that guides you through the process of
defining a recovery scenario. You can specify one or more operations that enable the test run to
continue after an exception event occurs. This functionality is especially useful during
unattended test runs, when errors or crashes could interrupt the testing process until manual
intervention occurs.
Silent Installation Now you can install WinRunner in an unattended mode using previously
recorded installation preferences. This feature is especially beneficial for those who use
enterprise software management products or any automated software distribution mechanisms.
Enhanced Integration with TestDirector WinRunner works with both TestDirector 6.0, which
is client/server-based, and TestDirector 7.x, which is Web-based. When reporting defects from
WinRunner’s test results window, basic information about the test and any checkpoints can be
automatically populated in TestDirector’s defect form. WinRunner now supports version control,
which enables updating and revising test scripts while maintaining old versions of each test.
Support for Terminal Servers Support for Citrix and Microsoft Terminal Servers makes it
possible to open several window clients and run WinRunner on each client as a single user. Also,
this can be used with LoadRunner to run multiple WinRunner Vusers.

Support for More Environments WinRunner 7.5 includes support for Internet Explorer 6.x and
Netscape 6.x, Windows XP and Sybase’s PowerBuilder 8, in addition to 30+ environments

3
already supported by WinRunner 7.
WinRunner provides the most powerful, productive and cost-effective solution for verifying
enterprise application functionality. For more information on WinRunner, contact a Mercury
Interactive local representative for pricing, evaluation, and distribution information.
WinRunner(Features & Benefits)
Test functionality using multiple data combinations in a single test
WinRunner’s DataDriver Wizard eliminates programming to automate testing for large volumes
of data. This saves testers significant amounts of time preparing scripts and allows for more
thorough testing.Significantly increase power and flexibility of tests without any programming
The Function Generator presents a quick and error-free way to design tests and enhance scripts
without any programming knowledge. Testers can simply point at a GUI object, and WinRunner
will examine it, determine its class and suggest an appropriate function to be used.
Use multiple verification types to ensure sound functionality
WinRunner provides checkpoints for text, GUI, bitmaps, URL links and the database, allowing
testers to compare expected and actual outcomes and identify potential problems with numerous
GUI objects and their functionality.

Verify data integrity in your back-end database

Built-in Database Verification confirms values stored in the database and ensures transaction
accuracy and the data integrity of records that have been updated, deleted and added.
View, store and verify at a glance every attribute of tested objects
WinRunner’s GUI Spy automatically identifies, records and displays the properties of standard
GUI objects, ActiveX controls, as well as Java objects and methods. This ensures that every
object in the user interface is recognized by the script and can be tested.

Maintain tests and build reusable scripts

The GUI map provides a centralized object repository, allowing testers to verify and modify any
tested object. These changes are then automatically propagated to all appropriate scripts,
eliminating the need to build new scripts each time the application is modified.

4
Test multiple environments with a single application
WinRunner supports more than 30 environments, including Web, Java, Visual Basic, etc. In
addition, it provides targeted solutions for such leading ERP/CRM applications as SAP, Siebel,
PeopleSoft and a number of others

NAVIGATIONAL STEPS FOR WINRUNNER LAB-EXERCISESUsing Rapid Test Script

wizard
• Start->Program Files->Winrunner->winruner
• Select the Rapid Test Script Wizard (or) create->Rapid Test Script wizard
• Click Next button of welcome to script wizard
• Select hand icon and click on Application window and Cilck Next button
• Select the tests and click Next button
• Select Navigation controls and Click Next button
• Set the Learning Flow(Express or Comprehensive) and click Learn button
• Select start application YES or NO, then click Next button
• Save the Startup script and GUI map files, click Next button
• Save the selected tests, click Next button
• Click Ok button
• Script will be generated.then run the scripts. Run->Run from top
• Find results of each script and select tools->text report in Winrunner test results.

Using GUI-Map Configuration Tool:

• Open an application.
• Select Tools-GUI Map Configuration;Windows pops-up.
• Click ADD button;Click on hand icon.
• Click on the object, which is to be configured. A user-defined class for that object is added to
list.
• Select User-defined class you added and press ‘Configure’ button.
• Mapped to Class;(Select a corresponding stanadard class from the combo box).

5
• You can move the properties from available properties to Learned Properties. By selecting
Insert button
• Select the Selector and recording methods.
• Click Ok button
• Now, you will observe Winrunner indentifying the configured objects.
Using Record-ContextSensitive mode:
• Create->Record context Sensitive
• Select start->program files->Accessories->Calculator
• Do some action on the application.
• Stop recording
• Run from Top; Press ‘OK’.
Using Record-Analog Mode:
• Create->Insert Function->from function generator
• Function name select ‘invoke_application’ from combo box).
• Click Args button; File: mspaint.
• Click on ‘paste’ button; Click on ‘Execute’ button to open the application; Finally click on
‘Close’.
• Create->Record-Analog.
• Draw some picture in the paintbrush file.
• Stop Recording
• Run->Run from Top; Press ‘OK’.
GUI CHECK POINTS-Single Property Check:
• Create->Insert function->Function Generator-> (Function name:Invoke_application; File
:Flight 1a)
• Click on’paste’ and click on’execute’ & close the window.
• Create->Record Context sensitive.
• Do some operations & stop recording.
• Create->GUI Check Point->For single Property.
• Click on some button whose property to be checked.
• Click on paste.
• Now close the Flight1a application; Run->Run from top.

6
• Press ‘OK’ it displays results window.
• Double click on the result statement. It shows the expected value & actual value window.
GUI CHECK POINTS-For Object/Window Property:
• Create->Insert function->Function Generator-> (Function name:Invoke_application;
File :Flight 1a)
• Click on’paste’ and click on’execute’ & close the window.
• Create->Record Context sensitive.
• Do some operations & stop recording.
• Create->GUI Check Point->Object/Window Property.
• Click on some button whose property to be checked.
• Click on paste.
• Now close the Flight 1a application; Run->Run from top.
• Press ‘OK’ it displays results window.
• Double click on the result statement. It shows the expected value & actual value window.
GUI CHECK POINTS-For Object/Window Property:
• Create->Insert function->Function Generator-> (Function name:Invoke_application;
File :Flight 1a)
• Click on’paste’ and click on’execute’ & close the window.
• Create->Record Context sensitive.
• Do some operations & stop recording.
• Create->GUI Check Point->For Multiple Object.
• Click on some button whose property to be checked.
• Click on Add button.
• Click on few objects & Right click to quit.
• Select each object & select corresponding properties to be checked for that object: click ‘OK’.
• Run->Run from Top. It displys the results.
BITMAP CHECK POINT:
For object/window.
• Create->Insert function->Function Generator-> (Function name:Invoke_application;
File :Flight 1a)
• Click on’paste’ and click on’execute’ & close the window.

7
• Create->Record Context sensitive.
• Enter the Username, Password & click ‘OK’ button
• Open the Order in Flight Reservation Application
• Select File->Fax Order& enter Fax Number, Signature
• Press ‘Cancel’ button. • Create->Stop Recording.
• Then open Fax Order in Flight Reservation Application
• Create->Bitmap Check->For obj.window;
• Run->run from top.
• The test fails and you can see the difference.
For Screen Area:
• Open new Paint Brush file;
• Create->Bitmapcheck point->from screen area.
• Paint file pops up; select an image with cross hair pointer.
• Do slight modification in the paint file(you can also run on the same paint file);
• Run->Run from Top.
• The test fails and you can see the difference of images.
DATABASE CHECK POINTS
Using Default check(for MS-Access only)
• Create->Database Check Point->Default check
• Select the Specify SQL Statement check box
• Click Next button
• Click Create button
• Type New DSN name and Click New button
• Then select a driver for which you want to set up a database & double clcik that driver
• Then select Browse button and retype same DSN name and Click save button.
• Click Next button & click Finish button
• Select database button & set path of the your database name
• Click ‘OK’ button & then Click the your DSN window ‘OK’ button
• Type the SQL query in SQL box
• Theb click Finish button Note : same process will be Custom Check Point

8
Runtime Record Check Point.
• Repeat above 10 steps.
• Type query of two related tables in SQL box Ex:
select Orders.Order_Number, Flights.Flight_Number from Orders, Flights
whereFlight.Flight_Number=Orders.Flight_Number.
• Select Finish Button
• Select hand Icon button& select Order No in your Application
• Click Next button.
• Select hand Icon button& select Filght No in your Application
• Click Next button
• Select any one of the following check box
1. One match record
2. One or more match records.
3. No match record
• select Finish button the script will be generated.
Synchronization Point For Obj/Win Properties:
• Open start->Programs->Win Runner->Sample applications->Flight1A.
• Open winrunner window
• Create->RecordContext Sensitive
• Insert information for new Order &click on “insert Order” button
• After inserting click on “delete” button
• Stop recording& save the file.
• Run->Run from top: Gives your results.
Without Synchronization:
• settings->General Options->Click on “Run” tab. “Timeout for checkpoints& Cs
statements’value:10000 follow 1 to 7->the test display on “Error Message” that “delete” button
is disabled.
With Synchronization:
• Keep Timeout value:1000 only
• Go to the Test Script file, insert pointed after “Insert Order” button, press statement.
• Create->Synchronization->For Obj/Window Property

9
• Click on”Delete Order” button & select enable property; click on “paste”.
• It inserts the Synch statement.
For Obj/Win Bitmap:
• Create-> Record Context Sensitive.
• Insert information for new order & click on “Insert order” button
• Stop recording & save the file.
• Go to the TSL Script, just before inserting of data into “date of flight” insert pointer.
• Create->Synchronization->For Obj/Win Bitmap is selected.
• (Make sure flight reservation is empty) click on “data of flight” text box
• Run->Run from Top; results are displayed. Note Keep “Timeout value” :1000)
Get Text: From Screen Area:
(Note: Checking whether Order no is increasing when ever Order is created)
• Open Flight1A; Analysis->graphs(Keep it open)
• Create->get text->from screen area
• Capture the No of tickets sold; right clcik &close the graph
• Now , insert new order, open the graph(Analysis->graphs)
• Go to Winrunner window, create->get text->from screen area
• Capture the No of tickets sold and right click; close the graph
• Save the script file
• Add the followinf script; If(text2==text1) tl_step(“text comparision”,0,”updateed”); else tl_step(“text
comparision”,1,”update property”);
• Run->Run from top to see the results.
Get Text: For Object/Window:
• Open a “Calc” application in two windows (Assuming two are two versions)
• Create->get text->for Obj/Window
• Click on some button in one window
• Stop recording
• Repeat 1 to 4 for Capture the text of same object from another “Calc” application.
• Add the following TSL(Note:Change “text” to text1 & text2 for each statement) if(text1==text2)
report_msg(“correct” text1); Else report_msg(“incorrect” text2);
• Run & see the results
Using GUI-Spy:Using the GUI Spy, you can view and verify the properties of any GUI object on
selected application
• Tools->Gui Spy…
• Select Spy On ( select Object or Window)
• Select Hand icon Button
• Point the Object or window & Press Ctrl_L + F3.
• You can view and verify the properties.

10
Using Virtual Object Wizard:Using the Virtual Object wizard, you can assign a bitmap to a standard
object class, define the coordinates of that object, and assign it a logical name
• tools->Virtual Object Wizard.
• Click Next Button
• Select standard class object for the virtual object Ex: class:Push_button
• Click Next button
• Click Mark Object button
• Drag the cursor to mark the area of the virtual object.
• Click Next button
• Assign the Logical Name, This name will appear in the test script when you record object.
• Select Yes or No check box
• Click Finish button
• Go to winrunner window & Create->Start Recording.
• Do some operations
• Stop Recording
Using Gui Map Editor:Using the GUI Map Editor, you can view and modify the properties of any GUI
object on selected application. To modify an object’s logical name in a GUI map file
• Tools->GUI Map Editor
• Select Learn button
• Select the Application A winrunner message box informs “do you want to learn all objects within the
window” & select ‘yes’’ button.
• Select perticular object and select Modify Button
• Change the Logical Name& click ‘OK’ Button
• Save the File
To find an object in a GUI map file:• Choose Tools > GUI Map Editor.
• Choose View > GUI Files.
• Choose File > Open to load the GUI map file.
• Click Find. The mouse pointer turns into a pointing hand.
• Click the object in the application being tested. The object is highlighted in the GUI map file.
To highlight an object in a Application:• Choose Tools > GUI Map Editor.
• Choose View > GUI Files.
• Choose File > Open to load the GUI map file.
• Select the object in the GUI map file
• Click Show. The object is highlighted in the Application.
Data Driver Wizard• Start->Programs->Wirunner->Sample applications->Flight 1A
• Open Flight Reservation Application
• Go to Winrunner window
• Create->Start recording
• Select file->new order, insert the fields; Click the Insert Order
• Tools->Data Table; Enter different Customer names in one row and Tickets in another row.
• Default that two column names are Noname1 and Noname2.
• Tools->Data Driver Wizard
• Click Next button &select the data table
• Select Parameterize the test; select Line by Line check box

11
• Click Next Button
• Parameterize each specific values with column names of tables;Repeat for all
• Finalli Click finish button.
• Run->Run from top;
• View the results.
Merge the GUI Files:Manual Merge
• Tools->Merge GUI Map Files A WinRunner message box informs you that all open GUI maps will be
closed and all unsaved changes will be discarded & click ‘OK’ button.
• Select the Manual Merge. Manual Merge enables you to manually add GUI objects from the source to
target files.
• To specify the Target GUI map file click the browse button& select GUI map file
• To specify the Source GUI map file. Click the add button& select source GUI map file.
• Click ‘OK’ button
• GUI Map File Manual Merge Tool Opens Select Objects and move Source File to Target File
• Close the GUI Map File Manual Merge Tool
Auto Merge
• Tools->Merge GUI Map Files A WinRunner message box informs you that all open GUI maps will be
closed and all unsaved changes will be discarded & click ‘OK’ button.
• Select the Auto Merge in Merge Type. If you chose Auto Merge and the source GUI map files are
merged successfully without conflicts,
• To specify the Target GUI map file click the browse button& select GUI map file
• To specify the Source GUI map file.
• Click the add button& select source GUI map file.
• Click ‘OK’ button A message confirms the merge.
Manually Retrive the Records form Database
• db_connect(query1,DSN=Flight32);
• db_execute_query(query1,select * from Orders,rec);
• db_get_field_value(query1,#0,#0);
• db_get_headers(query1, field_num,headers);
• db_get_row(query1,5,row_con);
• db_write_records(query1,,c:\\str.txt,TRUE,10);

12
EX.NO:1
Checking the details of flight reservation using the GUI spy
DATE:

AIM
To perform the GUI SPY using Record Context Sensitive Mode in WinRunner.

PROCEDURE
STEP 1: StartAll ProgramWinRunnerWinRunner.
STEP 2: Create a new test script.
STEP 3: Create RecordSelect Record Context Sensitive.
STEP 4: Go to StartAll ProgramsWinRunnerSample ApplicationFlight 4A.
STEP 5: A login window appears in that enter the Username and password.
STEP 6: Stop the recording.
STEP 7: Go to ToolsSelect spy.
STEP 8: Select an object in Flight Reservation window, that will be displayed on the
GUI SPY dialog box
STEP 9: Freeze the GUI SPY dialog box, by pressing Ctrl+F3 and then close the
window.
STEP10: Go to FileExit in the Flight Reservation window.
STEP11: Save the program.
STEP12: RunSelect Run from Top.
STEP13: The required output has been obtained successfully.
STEP14: Test Result will be generated.

13
OUTPUT:

14
EX.NO:2
Testing Scripts are checked in an Flight Reservation Application
DATE:

AIM:
To perform the calculation using Record Context Sensitive Mode in WinRunner.

PROCEDURE:
STEP 1: StartAll ProgramWinRunnerWinRunner.
STEP 2: Create a new test script.
STEP 3: Create RecordSelect Record Context Sensitive.
STEP 4: Go to StartAll ProgramsAccessoriesCalculator.
STEP 5: Perform some calculation operation.
STEP 6: Stop the recording and save it.
STEP 7: Call the test in new test and save it.
STEP 8: Run-Select Run from Top.
STEP 9: The required output has been obtained successfully.
STEP10: Test Result will be generated.

15
OUTPUT:

16
EX.NO:3
Sequential process are recorded are done and then it is checked
DATE:

AIM:
To perform the Data Driven Wizard using Record Context Sensitive Mode in
WinRunner.

PROCEDURE:
STEP 1: StartAll ProgramWinRunnerWinRunner.
STEP 2: Create a new test script.
STEP 3: Create RecordSelect Record Context Sensitive.
STEP 4: Go to StartAll ProgramsWinRunnerSample ApplicationFlight 4A.
STEP 5: A login window appears in that enter the Username and password.
STEP 6: Go to FileExit in the Flight Reservation and close the window.
STEP 7: Go to TableData Driven Wizard.
STEP 8: The Data Driven Wizard dialog box appears, enter the new column values.
STEP 9: Click the next button and then click Finish button.
STEP10: The data table window appears.
STEP11: Save the program.
STEP12: Run-Select Run from Top.
STEP13: The required output has been obtained successfully.

17
OUTPUT:

18
EX.NO:4
Text are tested in an sample application
DATE:

AIM
To perform the GUI Checkpoint using Record Context Sensitive Mode in WinRunner.

PROCEDURE:
STEP 1: StartAll ProgramWinRunnerWinRunner.
STEP 2: Create a new test script.
STEP 3: Create RecordSelect Record Context Sensitive.
STEP 4: Go to StartAll ProgramsWinRunnerSample ApplicationFlight 4A.
STEP 5: A login window appears in that enter the Username and password.
STEP 6: Select InsertGUI CheckpointFor Single property.
STEP 7: Select an object in Flight Reservation window and paste the object.
STEP 8: Select InsertGUI CheckpointFor object/window property.
STEP 9: Select InsertGUI CheckpointFor Multiple property.
STEP10: Click the add button in the multiple object and select the multiple object in the
Flight Reservation Window and then click ok.
STEP11: Stop the recording and save it.
STEP12: Run-Select Run from Top.
STEP13: The required output has been obtained successfully.
STEP14: Test Result will be generated.

19
OUTPUT:

20
EX.NO:5
Testing are based on the verification of both the images
DATE:

AIM
To perform Bitmap Checkpoint using Record Analog Mode in WinRunner.

PROCEDURE
STEP 1: StartAll ProgramWinRunnerWinRunner.
STEP 2: Create a new test script.
STEP 3: Create RecordSelect Record Analog.
STEP 4: Go to StartAll ProgramsAccessoriesPaint.
STEP 5: Perform any paint operation.
STEP 6: Stop the recording .
STEP 7: Go to InsertBitmap CheckpointFor object/window property.
STEP 8: Save the program.
STEP 9: Run-Select Run from Top.
STEP10: The required output has been obtained successfully.
STEP11: Test Result will be generated.

21
OUTPUT:

22
EX.NO: 6
Two or more applications are run simulations process is done
DATE:

AIM
To perform the paint using Record Analog Mode in WinRunner.

PROCEDURE
STEP1: StartAll ProgramWinRunnerWinRunner.
STEP2: Create a new test script.
STEP3: Create RecordSelect Record Analog.
STEP4: Go to StartAll ProgramsAccessoriesPaint.
STEP5: Perform any paint operation.
STEP6: Stop the recording and save it.
STEP7: Run-Select Run from Top.
STEP8: The required output has been obtained successfully.
STEP9: Test Result will be generated.

23
OUTPUT:

24
EX.NO:7

DATE:
To test synchronize tests for the application

AIM:
To perform the Synchronization Checkpoint using Record Context Sensitive Mode in
WinRunner.

PROCEDURE:
STEP 1: StartAll ProgramWinRunnerWinRunner.
STEP 2: Create a new test script.
STEP 3: Create RecordSelect Record Context Sensitive.
STEP 4: Go to StartAll ProgramsWinRunnerSample ApplicationFlight 4A.
STEP 5: A login window appears in that enter the Username and password. A Flight
Reservation window appears in that do the insertion, updation and deletion operation.
STEP 6: Go to InsertSynchronization CheckpointFor object/windows property.
STEP 7: Select an object in Flight Reservation window and paste the object.
STEP 8: Stop the recording and save the program.
STEP 9: Run-Select Run from Top.
STEP10: The required output has been obtained successfully.
STEP11: Test Result will be generated.

25
OUTPUT:

26