Performance Test Plan

Test Plan
Version 1.0 | September 18, 2007
Copyright Information
This document is the exclusive property of CompnayConsulting Private Limited he recipient agrees that he/she
may not copy, transmit, use or disclose the confidential and propriety information set forth herein by any means
without the expressed written consent of Compnay. By accepting a copy hereof, the recipient agrees to adhere
to and be bound by these conditions to the confidentiality of Compnay's practices and procedures; and to use
these documents solely for responding to Compnay's operations methodology.
© All rights reserved CompnayConsulting Private Limited, 2005

Revision History
Version Pages Description Date Author/Reviewer
0.1 All Initial Draft l Pooja Mehta, Karthikeyan
Selvaraj

References
Reader should read this document in conjunction with the following documents

No Document Name Version File Name Location

1
2

Proprietary and Confidential. © CompnayConsulting Private Limited ii

Opsolight+ | Performance Test Plan

Table of Contents

1 PURPOSE OF THE DOCUMENT.................................................................................................................2

2 SCOPE OF THE DOCUMENT......................................................................................................................2

2.1 DEFINITIONS, ABBREVIATION AND ACRONYMS............................................................................................2
2.2 PROBLEM STATEMENT................................................................................................................................2
3 TESTING STRATEGY AND APPROACH...................................................................................................2
3.1 LOAD TESTING...........................................................................................................................................2
3.2 TOOLS USED FOR LOAD TESTING:...............................................................................................................2
3.3 PLANNED TESTING CYCLES.........................................................................................................................2
3.4 METRICS TO BE MEASURED.........................................................................................................................2
3.5 FEATURES NOT TESTED...............................................................................................................................2
3.6 ASSUMPTIONS & LIMITATIONS....................................................................................................................2
4 TEST SETUP...................................................................................................................................................2
4.1 TEST ENVIRONMENTS.................................................................................................................................2
5 PERFORMANCE TEST EXECUTION.........................................................................................................2
5.1 PERFORMANCE TEST..................................................................................................................................2
5.2 ENTRY CRITERIA........................................................................................................................................2
5.3 EXIT CRITERIA...........................................................................................................................................2
6 TEST SCHEDULE AND ESTIMATES..........................................................................................................2
6.1 TEST SCHEDULE.........................................................................................................................................2
6.2 DELIVERABLES...........................................................................................................................................2
7 PROGRAM PLAN FOR DEFINITION PHASE...........................................................................................2

8 PROGRAM PLAN FOR IMPLEMENTATION PHASE..............................................................................2

8.1 Assumptions..............................................................................................................................................2

Opsolight+ Performance test plan | Version 1.0 4 of 11

Proprietary and Confidential. © CompnayConsulting Private Limited
Opsolight+ | Performance Test Plan

1 Purpose of the Document

This document will serve as the reference document for the Compnay’s scope of activities for the
performance testing of the Unilever Opsolight+ Application.
This document covers the following topics:
 The strategy, responsibilities and schedule for the overall testing.
 Identify the project and software components that should be tested.
 List the scope of testing.
 List the deliverable elements.
 Identify the risks and assumptions in the project, if any.
 Define the entry and exit criteria for Load testing phase.
 Timelines of the project milestones.

2 Scope of the Document

This document describes the test plan for the Performance(Load) testing that shall be carried out for
the Unilever Opsolight+ application. Other types of testing are not in the scope of this document.

 Understanding the application functionality and it’s technical architecture from the Performance
testing perspective.
 Performance test scenarios are identified by Compnay.
 Creation of Test Scripts with various settings and options.
 Execution of Test Scripts.
 Server resource are monitered by ULL.
 Prepare performance testing analysis graphs and reports submitted to ULL Team.
 Performance bottlenecks are identified by ULL team based upon Compnayperformance test
reports.

Following table lists out the performance testing scenarios that will be the benchmarks for
performance testing.

Types of Transactions
Scenarios
Promotion Dashboard Login
In Process Click the Promotion link on Home Dashboard
Search for promotions date ranging from 1Sept to 31 Dec
Click on a promotion in Plan state
Logout
Promotion Dashboard Login
Approved Click the Promotion link on Home Dashboard
Click on Approved link on Promotion Dashboard
Search for promotions date ranging from 1Sept to 31 Dec
Click on a promotion
Logout
Promotion Creation Login
Click on the Promotion link on Home Dashboard

Opsolight+ Performance test plan | Version 1.0 5 of 11

Proprietary and Confidential. © CompnayConsulting Private Limited
Opsolight+ | Performance Test Plan

Click on Create a new Promotion link on Promotion Dashboard

Header page
Detail Mechanics
Account Allocation
Inv types & Products
Investment Details
Investment Planning
Evaluation
Preview
Logout

2.1 Definitions, Abbreviation and Acronyms

The terms in use in the document are explained/expanded below

Acronym Description
Vugen Virtual user generator – used to generate vuser script
.net Microsoft dot net technology

2.2 Problem Statement

The response time for DashBoards(Budget and Promotion) and Promotion Creation i.e navigating
through pages is very high. The Load tests are to identify the potential performance bottlenecks on
the application.

High Level Application Architecture

3 Testing Strategy and approach

Compnaytesting team will study and understand the application functionality from the performance
testing perspective.ULL team along with Compnayteam identifed performance test scenarios and
Compnaytesting team will develop test scripts for the identified scenarios and execute the same ,which
would aim at finding the potential performance bottlenecks.

Opsolight+ Performance test plan | Version 1.0 6 of 11

Proprietary and Confidential. © CompnayConsulting Private Limited
Opsolight+ | Performance Test Plan

LoadRunner is the tool identified by ULL which will be used for conducting performance testing and to
generate test execution reports. LoadRunner tool is installed at ULL’s infrastructure and can be
accessed via remote access software.

Testdata will be prepared by Compnayunder the guidance of ULL. Compnaywill demonstrate scenarios
for a single user to ensure Unilever Opsolight+ application is stable and does not generate errors during
script execution.ULL will review the test data before the load test to validate completeness.
Compnaywill rerun the scripts for 50 Vusers. These users will conduct all types of transactions on the
application in the available test environment. The performance parameters pertaining to the system
(Web server and database) would be monitored by ULL SA/DBA. Should failures occur which point to
testdata being incomplete or erroneous, Compnaywill make fixes as needed.

QA will execute the load-testing scripts created by Compnayand also manually test Unilever Opsolight+
to visually verify acceptance criteria is met.

Tests will be conducted with the load simulated starting with 10 Vusers.Once base line test is satisfied,
Load test is planned for 50 Vusers.

After test execution, Compnaywould, thereafter, generate the test reports to analyze the results. All the
issues identified during each iteration and load testing results (including Web & Database performance
monitor data) will be reported to ULL . Compnaywill prepare performance test analysis graphs, reports
and submit to ULL Team.Performance bottlenecks will be identified by ULL DBA /SA who will look into
the bottlenecks to find what needs to be fine tuned or what the abnormal issues they saw and will
provide that information to Compnay.

3.1 Load Testing

Load testing will be carried out under varying workloads to assess and evaluate the ability of the
system under test to continue to function properly under these different workloads. The goal of
load testing is to determine and ensure that the system functions properly beyond the expected
maximum workload. Additionally, load testing evaluates the performance characteristics
(response times, transaction rates, and other time sensitive issues).

 Determine the serviceability of the system for a volume of 50 concurrent users.

 Measure response times for users

Compnaysimulates the average and peak loads as shown in the table below using Loadrunner.

Scenario
Promotion Creation Settings
50 concurrent users
Ramp up 5 Vusers every 3 minutes
Ramp down 5 Vusers every 3 minutes
Duration (Peak Load) 5 minutes
Pacing between iterations 10 seconds

3.2 Tools used for Load Testing:

Vugen

Opsolight+ Performance test plan | Version 1.0 7 of 11

Proprietary and Confidential. © CompnayConsulting Private Limited
Opsolight+ | Performance Test Plan

Vugen records all of the objects on every page that you visit and automatically inserts tests to validate
the objects. The components of each page are represented graphically in the Vuser scripts and can be
enhanced for requirements.

Controller
Controller provides the way to test the scalability of applications. Controller emulates virtual users accessing
the site simultaneously, and measures the effect of the load on application performance. It ensures that your
tests will closely correlate with real user-load so you can confidently use Loadrunner results to help make
key decisions about your system’s architecture, tuning, and hosting alternatives.

Analyzer
Analyzer lets you generate a variety of reports based on performance data and statistics from a Controller.

Description Tool

Tool for Performance Testing Loadrunner 8.1

3.3 Planned testing cycles

Load testing will be done on Unilever Opsolight+ Web Application against a range of operational
conditions and factors including network bandwidth, data volumes and transaction frequency. The test
cycles shall be run on the network measuring performance from 25 Vusers to 50 Vusers.

The test cycle shall be run for 10 users initially. The test shall be stopped if application crashes before
reaching 50 users and issue shall be reported to ULL.The response time shall be noted for 50
concurrent users before stopping the test. If the response time is exceeding the benchmark limit, load
test shall be stopped until development team fixes the issue. The response times will be noted for the
following user loads.

 10 Vusers

 30 Vusers

 40 Vusers

 50 Vusers

3.4 Metrics to be measured

Client Side Primary Metrics:

 Response Time
 Throughput
 Average Response Time (Measured)
 Transaction Summary

3.5 Features not tested

Functional testing of all the Transactions is not in the scope of this test.

Opsolight+ Performance test plan | Version 1.0 8 of 11

Proprietary and Confidential. © CompnayConsulting Private Limited
Opsolight+ | Performance Test Plan

3.6 Assumptions & Limitations

1. ULL will provide remote access connectivity.

2. The inability to provide the replica of the production environment would result in conducting the
performance testing on the available test environment and the results would only hold good for the
given environment. The same system performance could not be expected or guaranteed on the
production architecture.
3. The performance testing will begin only if the application is stable with respect to functionality and
usability.
4. Scripts are generated based on the current version of the application. Any enhancement on the
current version of the application would require rescripting.
5. The performance measures are applicable to available functionality of the system at the time
of testing.

4 Test Setup

4.1 Test Environments

The following table sets forth the system resources for the project

Resource Name / Type

Web server Microsoft IIS

Data Base Server Ms SQL 2005
Loadrunner 8.1

5 Performance Test execution

5.1 Performance Test

1. Measure the application performance behaviors and characteristics (transaction response

times, throughput) that will identify the serviceability (concurrent users) and peak performance
of the system.

2. The results of these tests would give symptoms of slowness and facilitate bottleneck analysis.

3. This test is executed for each transaction increasing the no. of virtual users.

4. The LoadRunner will coordinate with the multiple Vusers for load generation.

5. If the test script execution failed due to the problem in the application, the
test is aborted and the next script is executed.

Opsolight+ Performance test plan | Version 1.0 9 of 11

Proprietary and Confidential. © CompnayConsulting Private Limited
Opsolight+ | Performance Test Plan

5.2 Entry Criteria

Following should be satisfied for the Performance testing to start:

 System testing is done / application is stable.

 Load Test Plan with performance objectives.

 Performance Specifications.

 Testing Tool to be used for test execution.

 Network connectivity is established to access controller remotely.

5.3 Exit Criteria

In order for Load Testing to be considered successful the Load Scripts must be successfully be executed
under the following conditions:

 All mentioned scenarios executed by performance test team.

 Simulate 25 to 50 virtual users.

6 Test Schedule and Estimates

6.1 Test Schedule

The planned schedule is provided below. However, this schedule is subject to change based on the system
availability and bugs in the application.

Milestone / Deliverable Planned Date Owner

Detailed steps for identified Sept 17 Compnay

scenarios

Load Test Plan Sept 18 Compnay

Test Script Sept 28 Compnay

Test execution Report Compnay

Consolidated Test execution Compnay/ULL

& Analysis Report
Handover of test scripts to Compnay
QA team

6.2 Deliverables

The following deliverables will be given to the client during performance testing:

Opsolight+ Performance test plan | Version 1.0 10 of 11

Proprietary and Confidential. © CompnayConsulting Private Limited
Opsolight+ | Performance Test Plan

 Performance test plan.

 Test Execution Reports.

7 Program Plan for Definition Phase

The following are the activities envisaged during this phase:

 Environment setup and test data generation.

 Script Generation.
 Execution.
 Metrics & Reports.

8 Program Plan for Implementation phase

8.1 Assumptions

 Test environment similar to production will be available for the performance testing team.

 ULL DBA/SA will monitor servers.

 Any major failure of the test bed, software issues would require revision of the Test plan

 Application/System is considerably stable in terms of the basic functionality.

 The delays occuring due to application accessibility or any other failures will be tracked reported
and assessed periodically for early resolution, risk projections

 The Test scripts would be developed and tested on the browser Internet Explorer version 6.0 and
above

Opsolight+ Performance test plan | Version 1.0 11 of 11

Proprietary and Confidential. © CompnayConsulting Private Limited