FACULTY OF TECHNOLOGY

Department of Information Technology

1IT0601 - Software Engineering Lab
3. Study of Various Testing Tools: Win Runner 8.0: Checkpoints in WinRunner. Data
Driver and Batch Testing. Load Runner 8.0: VuserScript Creation, Execution and
Result using Load Runner, Test Director 8.0: Site Administrator, Understanding
Test Director.

 WinRunner 8.0
 Introduction
WinRunner records the operations you perform and generates statements in TSL, Mercury
Interactive's Test Script Language. These statements appear as a script in a WinRunner test
window. Before you begin recording a test, you should plan the main stages of the test and select
the appropriate record mode.

 Checkpoints in WinRunner:
1) GUI Checkpoints: to check and ensure details about GUI objects.
2) Text Checkpoints: to verify GUI objects contents.
3) Database Checkpoints: to check the data set.
4) Bitmap Checkpoints: to compare a snapshot to an earlier version of the same test.

 Data Driver Use In Win Runner:

An application has to be tested with multiple sets of data. The automation test script written for
one input can be used for number of inputs using data driven test in Winrunner. The test script
has to be converted into the data driven test by creating a corresponding data table with the sets
of data you want to test.

 Steps in creating data driver testing

1) Adding statements to your script that open and close the data table.
2) Adding statements and functions to the test so that it will read from the data table and run
in a loop while it applies each set of data.
3) Replacing the fixed values in the recorded statements and checkpoint statements with

92210104003 14
 FACULTY OF TECHNOLOGY
Department of Information Technology
1IT0601 - Software Engineering Lab
parameters, known as parameterizing the test.

 Features of Win Runner

1) Learning: Recognition of objects and windows in our application by WinRunner
2) Recording: WinRunner records over manual business operation in TSL.
3) Edit Script. depends on corresponding manual test, test engineer inserts check points in
to that record script.
4) Run Script
5) Analyse Results

 Batch Testing:
By creating a single batch test, you can run an entire suite of tests unattended. You
can start a batch test run, go to lunch, and come back to review the results when
the run is finished.

A batch test looks and behaves like a regular test script, except for two main differences:

1. It contains call statements, which open other tests

For example: call "c:\\qa\\flights\\lesson8"();

During a test run, WinRunner interprets a call statement, and then opens and runs the “called” test.
When the called test is done, WinRunner returns to the batch test and continues the run.

2. You choose the Batch Run option in the Options dialog box (Settings > Options) before running the
test. This option instructs WinRunner to suppress messages that would otherwise interrupt the test. For
example, if WinRunner detects a bitmap mismatch, it does not prompt you to pause the test run.

When you review the results of a batch test run, you can see the overall results of the batch test (pass
or fail), as well as the results of each test called by the batch test.

 Load Runner 8.0

 Introduction:
LoadRunner is a software testing tool provided by Micro Focus used to perform load/stress
tests in your applications, measuring the behaviour and performance of your system under high
workload. LoadRunner simulates user activity by generating requests that are executed against
an application.

92210104003 15
 FACULTY OF TECHNOLOGY
Department of Information Technology
1IT0601 - Software Engineering

 Steps to creating VuserScript :

1) Open VuGen and select File > New Script and Solution, or click the New
Solution button.

2) In the Create a New Script dialog box, select Single Protocol or Multiple Protocols from
the Category list.

3) Select a protocol from the Protocols list.

4) In the Script Name box, enter a name for the script.

5) Click Create to create the Vuser script.

 Execution and Result

 Scenario Execution:
Scenario execution is where you emulate user load on the server by instructing multiple VUsers
to perform tasks simultaneously.

You can set the level of a load by increasing and decreasing the number of VUsers that perform
tasks at the same time.

This execution may result in the server to go under stress and behave abnormally. This is the
very purpose of the performance Testing. The results drawn are then used for detailed analysis
and root cause identification.

92210104003 16
 FACULTY OF TECHNOLOGY
Department of Information Technology
1IT0601 - Software Engineering

 Result:
During scenario execution, LoadRunner records the performance of the application under
different loads. The statistics drawn from test execution are saved and details analysis is
performed. The ‘HP Analysis’ tool generates various graphs which help in identifying the root
causes behind a lag of system performance, as well as a system failure.

 Some graph which is use in this scenario:

I. Time to the First buffer
II. Transaction Response Time
III. Average Transaction Response Time
IV. Hits Per Second

 Test Director 8.0:

 Introduction:
Test Director 8.0—Mercury Interactive's Web-based test management tool. You must have
access to the following modules: Requirements, Test Plan, Test Lab, and Defects. Test Director
Demo—a demonstration project that helps introduce you to. Test Director helps you organize test
runs by building test sets. A test set is a subset of the tests in your project, run together in order
to achieve a specific goal.

92210104003 17
 FACULTY OF TECHNOLOGY
Department of Information Technology
1IT0601 - Software Engineering

 Site Administrator Responsibility:

1) User Management: Creating, modifying, and deleting user accounts. Assigning roles and
permissions to users based on their responsibilities.

2) Project Management: Creating and configuring projects within Test Director. Defining project-
specific settings and configurations.

3) Customization: Customizing fields, workflows, and templates to align with project-specific needs.

4) Security: Ensuring secure access to projects and data. Managing security settings and access
control lists.

5) Backup and Recovery: Implementing and overseeing backup and recovery procedures to safeguard
project data.

 Understanding Test Detector

1) Test Planning: Creating test plans that outline the testing strategy and scope.

2) Test Design: Developing and organizing test cases based on requirements.

3) Test Execution: Executing test cases and recording results.

4) Defect Tracking: Logging and tracking defects found during testing.

92210104003 18