Performance Testing New Digital Infrastructure

A top tier retail bank engaged SQA Consulting in order to Performance, Stress & Volume Test their Digital Infrastructure. The bank was delivering circa £20 million pounds worth of change on a monthly basis. In order to ensure success, which incorporates repeatability, SQA Consulting advocated that the Performance related testing is decomposed into two separate stages: -

Stage 1

1. Establish Requirements
  • Establish Testing Objectives
  • Produced High Level Test Plan
  • Identify Risks
  • Identify Roles
  • Establish Terms of Reference
2. Analyse Application Under Test
  • Identified Critical Business Transactions
  • Transaction Profiles
  • User Profiles
  • Data Profiles
  • System Information
  • Revised the Project Plan
3. Define the Test Environment
  • Produce high level Test Environment Plan
  • AUT Software Specification
  • Security
  • AUT Hardware Specification
  • The Test Harness
  • Test Data

 

Stage 2

 

The second stage of the proof of concept will address the physical Load Test.

1. Create a Test Plan
  • Developed the Test Plan
  • Revised project plan
  • Test plan sign off with the test sponsor
  • Design Virtual Users
2. Design Virtual Users
  • Documented the Virtual Users
  • Test Data Definition
3. Build the Test
  • Build/verify an initial testing environment
  • Build the database, with sample test data
  • Created test data files required by Virtual Users
  • Installed Load & Performance products
  • Created the DB Virtual Users
  • Created the GUI Virtual Users
  • Set-up and test Monitoring tools
  • Prepared the Host machines
  • Created Test Scenarios
4. Execute the Test
  • Executed the tests as detailed in the test plan
  • Analysed Results
  • Reported on Findings

 

 

Our primary deliverables included:

1) Establish Requirements

 

 

 

Mandatory
  • High Level project plan
  • Terms of Reference
  • High level test plan
  • Role Definitions
  • Stage sign-off
Discretionary
  • System architecture plan
  • Existing testing methodology

2) Analyze Application Under Test

 

 

Mandatory
  • Transaction Details
  • Transaction Usage Profiles Data Requirements
  • Revised project plan
  • Background processes
  • Stage Sign Off
Discretionary
  • Existing SLA’s

3) Define the Test Environment

 

 

Mandatory
  • Test Environment Plan
  • Hardware Specification
  • Software Specification
  • Test Harness Specification
  • Test data Specification
  • Stage Sign Off
Discretionary
  • Security Review

 

 

 

Our secondary stage deliverables included:

1) Test Plan Creation

 

 

 

Mandatory
  • Test plan
  • Revised project plan
  • Sign off

2) Design Virtual Users

 

 

Mandatory
  • Script table
  • Test data definition
  • Stage Sign Off

3) Build the Test

 

 

Mandatory
  • Completed and tested Vusers
  • Complete data files
  • Propagated database
  • Complete Test Scenarios
  • Completed test environment
  • Stage Sign Off
Discretionary
  • Parameter documentation
  • Amendment documentation
  • Monitoring tools in place

4) Execute the Test

 

 

Mandatory
  • Review Test Tool Results
  • Test Execution Report
Discretionary
  • System Monitoring Report

5) Fixes and Recommendations

 

 

Mandatory
  • Suggestions on how to improve performance
  • Implemented changes in order to improve performance
  • Move to Full Performance Test Re-Execution