<Projects name>

SCDHHS Performance Test Plan

Prepared by:
Raja Gampa

South Carolina Department of Health and Human Services

(SCDHHS) Project Management Office (PMO)
 Contents
1 Revision History.........................................................................................................4
2 Approvals.....................................................................................................................4
3 Definitions....................................................................................................................5
4 Reference Documents.................................................................................................5
5 Project Overview.........................................................................................................5
6 Requirement Background..........................................................................................6
6.1 Objective of the Project.......................................................................................6
6.2 Objective of Performance Testing.....................................................................6
6.3 Project Contacts...................................................................................................6
7 Scope of Work.............................................................................................................6
7.1 System Architecture...........................................................................................6
7.2 Production vs Test Environment......................................................................8
7.3 Business Processes for Performance Testing..................................................9
7.4 Volumes and SLA’s..........................................................................................10
7.5 Peformacne Test Execution.............................................................................10
7.6 Tools used in the project..................................................................................10
7.7 Activities In Scope............................................................................................10
7.8 Scope Exclusions...............................................................................................11
7.9 Assumptions......................................................................................................11
7.10 Risks....................................................................................................................11
8 Performance Monitoring..........................................................................................12
9 Testing Schedule.......................................................................................................12
1 Revision History
Version No. Date Revised By Description of Change

2 Approvals
The undersigned acknowledge that they have reviewed the Master Test Plan and agree with the
information presented within this document. Changes to this plan will be coordinated with, and
approved by, the undersigned, or their designated representatives. The Project Sponsor will be
notified when approvals occur.

Signature: Date:
Print Name:
Title:
Role:

Signature: Date:
Print Name:
Title:
Role: Program Director

Signature: Date:
Print Name:
Title:
Role: Test Manager

Signature: Date:
Print Name:
Title:
Role:
3 Definitions
Term Meaning

4 Reference Documents
Documents Repository Path
Project Planning

5 Project Overview
<Give a details about project overview>

6 Requirement Background
6.1 Objective of the Project
< Give a details objective of project>

6.2 Objective of Performance Testing

6.3 Stakeholder Roles and Responsibilitys

 Role Name Extension

7 Scope of Work
7.1 System Architecture

Data Flow

Environment topology
7.2 Production vs Performance Testing Environment

Performance Testing Environment

Table 1: Performance Environment Site Requirements

Component No. of CPU/Node Memory Storage
Nodes/
machines

Production Details

Table 2: PROD Environment Site Requirements

Component No. of CPU/Node Memory Storage
Nodes/
machines

PROD vs PERF Details

Component Y/N Details

#
Do Test and Prod have the same number of Web
1 Servers?
Do Test and Prod Web Servers have the same
hardware configuration (CPU, Memory, Disk,
2 NIC’s, etc)?
Do Test and Prod have the same number of App
3 Servers?
Do Test and Prod App Servers have the same
hardware configuration (CPU, Memory, Disk,
4 NIC’s, etc)?
Do Test and Prod Database Servers have the
5 same amount of data?
6 Do Test and Prod DB Server(s) have the same
hardware configuration (CPU, Memory, Disk,
 NIC’s, etc)?

7.3 Business Processes for Performance Testing

The business processes below are considered in scope for performance testing.

# New/Existing Business Process Name Complexity Script Type

1
2
3

7.4 Volumes and SLA’s

The below mentioned SLAs has to be met by the application during performance testing and this
identifies part of the SUCCESS/FAIL criteria for tests.

External Internal Comments

Access  

No of Users*

Highest peak for

concurrent user access

What is the average

(Monday-Friday) for
concurrent user access

Script Name User Volume Transaction Volume/hr Response time(sec)

7.5 Peformacne Test Execution
Baseline Testing

Baseline Testing examines how a system performs under expected or normal load and creates a
baseline against which the other types of tests can be compared.
Pass Criteria: Find metrics for system performance under normal load.

Load Tests:
These tests will emulate the peak hourly load as on production servers.

Pass Criteria: 2 Load Tests where all SLA’s are met.

1 Stress Test:
This test is to find the break point, where the application breaks. We will increase user volumes up to
2X expected peak load. We will run for a steady state of 15 minutes at each user volume level.

Pass Criteria: Application doesn’t break at 2X load

7.6 Tools used in the project

Tools Details
IBM Rational Performance Tester To Generate load
PERFMON, NMON Monitoring Tool

7.7 Activities In Scope

The following activities are in scope of performance testing:

1. Requirement Gathering and Test Planning

2. Test Script Development
3. Test Execution, Monitoring
4. Test Results Reporting

7.8 Scope Exclusions

1. Functional testing activities.
 2. Test data setup activities to setup the data required for the transactions.
3. Hardware and other infrastructure-related enhancements
4. Any support activities and functionality issues for the existing production issues
5. Any architecture or database related changes.
6. Any performance issues arising out of third party applications.

7.9 Assumptions
The following assumptions are made:

1. This document must be completed prior to script creation.

2. Workflows to be scripted must be documented prior to script creation.
3. All Sev 1 and 2 defects must be resolved prior to script creation.
4. All testing will be performed in a dedicated test environment.
5. Performance test execution must happen on the same build of code that goes to production.
6. The database in test environment is sized similar to the production environment.

7.10 Risks

1. Scripts used in previous cycle of testing are often unreliable on new builds. This issue will
frequently cause additional time and cost for re-scripting on the latest build.
2. The need for Performance Tuning Activities, delays in providing code or environment, or
any other delays with the project may require additional time, effort and cost.
3. Code changes during scripting or execution will often cause script failures. It is advisable to
freeze code when performance scripting has started if possible.
4. There will likely be a delay in test execution if tuning requires the application to be
unavailable for the test execution.
5. Any delay in testing environment availability will impact on the script validation and test
execution schedule.

8 Performance Monitoring

Server Name Counter Name



Load Balancer (F5)

 Oracle WebLogic Server 12C

Database Server

9 Testing Schedule

Performance Testing Stage Start Date End Date

Performance test scope

Performance test scripting

Performance test execution

Performance tuning activities

Performance test closure