Load Software Test Plan (LSTP)

©2008 Doron Bar.
All Rights Reserve
<Product>
<Version>
Load Software Test Plan (LSTP)

Document Version 0.1
Date: dd/mm/yy
File name: 9254522.doc
Prepared by:
Page 1 of 11
© 2008 Doron Bar All Rights Reserved – Document can be used freely only without changing this footer!!!
©2008 Doron Bar. All Rights Reserve
Approval Path
Name Position Date Signature Comments

Web QA Team Leader
Head of Technical and Releases Dept.
Portal development team leader
Product manager
Document Version Control Page

File Name: 9254522.doc
Last Modified: 18 October 2008
Written By:
Document Date Author Approved Edited By Contents

version By
Page 2 of 11
Table of Contents
1. Introduction.................................................................................................................................................3
1.1 Purpose......................................................................................................................................................4
1.2 Scope..........................................................................................................................................................4
1.3 Terminology and Acronyms.....................................................................................................................4
1.4 References..................................................................................................................................................4
1.5 Overview....................................................................................................................................................5
2. Software Test Environment........................................................................................................................5

2.1 Software Items..........................................................................................................................................5
2.2 Hardware Items........................................................................................................................................5
2.2.1 Application Server.................................................................................................................................5
2.2.2 Web Server............................................................................................................................................5
2.2.3 DB server...............................................................................................................................................6
2.2.4 WebLoad probing clients ......................................................................................................................6
2.3 Data environment.....................................................................................................................................6
2.4 Installation, Testing and Control.............................................................................................................7
3. Test strategy.................................................................................................................................................8
3.1 Test Plan Strategy.....................................................................................................................................8
3.2 Load test techniques.................................................................................................................................8
3.2.1 Load oriented testing ............................................................................................................................8
3.2.2 Goals oriented........................................................................................................................................9
3.2.3 Stress tests.............................................................................................................................................9
3.3 Test Execution Strategy............................................................................................................................9
3.3.1 Test cycles.............................................................................................................................................9
4. Main processes..........................................................................................................................................10
5. Performance goals ....................................................................................................................................11
1. Introduction
This document serves as the Load Software Test Plan for the <Product>, <Version>.
Page 3 of 11
This document defines the ways of testing the <Product> application in load mode.
1.1 Purpose
The purpose of this LSTP is to define the requirements for testing <Product>. It is intended to serve a basis for
the translation of the RTM into the LSTD.
1.2 Scope
This document specifies the requirements for testing <Product>, which purpose is to be the working
environment of different members in an enterprise and to allow enterprise’s trading partners to plan
collaboratively.
The aim of the document is to present load test plan, that includes the following issues:
- Environment - hardware, software, data and installation;
- Test strategy
- Main <Product> processes used to create user profiles
- Performance goals
User profiles used in load tests are described in LSTD.
1.3 Terminology and Acronyms

LSTP – Load Software Test Plan
LSTD – Load Software Test Description
RTM – Requirements Matrix. Functional requirements defined by product management.
1.4 References
N Document Title File name (inc. path) Comments

o
.
(1)
LSTP
(2)
LSTD
(3)
RTM
Page 4 of 11
1.5 Overview
<Product> is a collaborative platform for Business-to-Business solutions,
Private Trading Networks and Trading Exchanges (e-Marketplaces). It is
the home page from which users can access information from the Suite.
From the <Product> site, the Demand Chain members receive on-line and
member specific information together with workflow assigned tasks,
messages, and exception alerts.
2. Software Test Environment

This section describes software and other resources required to test the <Product>.
2.1 Software Items

All systems are going to run on Windows <n>.
The Web Servers are <> and <>.
2.2 Hardware Items
2.2.1 Application Server

Attribute Value Comments
Application Server
CPU
Memory
Connection 100MB
line
2.2.2 Web Server

Attribut Value Comments
e
Web server
CPU
Memory
Operating system
*Note: Web Server and Application Server must run on the same machine, due to R&D constraints.
Page 5 of 11
2.2.3 DB server
e
Oracle version Mean
Connection line
2.2.4 WebLoad probing clients

e
CPU
Memory
Operating system
Connection line
2.3 Data environment

1. DB used:
Oracle user Machine Comments
2. DB characteristics:
Parameter Value Comments
Number of records in
data table
Sales history
Number of items
Number of locations
Number of series
3. Security Management preparations:

Create a group of Portal users for each of the profiles described in LSTD: p_profile_1, p_profile_2, etc.
Page 6 of 11
Each group will include users named in the following way: pX_Y, where X is the number of profile, Y is the
number of user. So that, p1_1 – is user number 1 belonging to Profile 1, p4_2 – user number 2 belonging to
Profile 4, etc.
2.4 Installation, Testing and Control
Component Machine Comments

Web Server + Appl. Server
Load Machine
Probing Client
Web Load Console
Page 7 of 11
3. Test strategy
3.1 Test Plan Strategy

The test planning is done in 2 main phases:
The Load software test plan that will describe the following topics:
• Test environment
• Test strategy
• Test execution procedures
• Goals
• Time table
The Load software test description will include the following topics:
• Common user profiles
• Load size and distribution
The load test plan will be done in the following stages:

1.Functional breakdown of the system.
2.Defining data environment.
3.Defining common users profiles.
4.Defining the requirement of the system.
5.Creating test cases (Agendas) that will cover all cases and possibilities of the system.
6.Combining several test cases to test scripts or expanding each test case to a single script that
contains test steps (creating Load Sessions).
3.2 Load test techniques

The following sessions are going to be executed:
3.2.1 Load oriented testing

Three load sizes will be defined:
1. Low – Executing the load sessions with few virtual clients in order to find the performance of the
system under low load conditions.
Page 8 of 11
2. Normal – Executing the load sessions under the normal load conditions at the customer site
3. High - Executing the load sessions under high load conditions at the customer site
3.2.2 Goals oriented

Defining the goals of the system for each transaction and execute the sessions
while increasing the amount of virtual clients in order to find the maximum virtual
clients that can use the system while keeping the performance goals.
3.2.3 Stress tests

Creating load sessions that contains all transactions in the system, and running
them in the maximum virtual clients for 24 hours.
3.3 Test Execution Strategy
3.3.1 Test cycles

The sessions are going to be executed in 2 cycles. The first cycle will include the
load test sessions. The second cycle will include the goals oriented tests and the
stress tests.
If necessary, 3rd cycle will be executed for regression tests.
Page 9 of 11
4. Main processes
This table summarizes the main processes available inside <Product>.
Process Comments
1. Log in
2. Personalize content layout on Portal page
3. Edit Tasks List view
4. Edit Available Worksheets view
5. Add new content
6. Edit existing content
7. Choose existing content from Navigation Bar
8. Send Worksheet as a task (from Available Worksheets
list)
9. Open Worksheet with <Product>from the list of
Available worksheets
10. Send a task for other Portal user
11. Open external links from Navigation Bar
12. Open On-Line Help
13. Send e-mail to Portal user (by clicking on Who’s On
Line list)
14. Navigation between <Product> pages with Path
Indicator
15. Log-out
Page 10 of 11
5. Performance goals
This paragraph identifies the basic screen actions and the goal performance time to perform each action. For
more details see also <Product> RTM.
Process Goal time Comments

Log-in 1 sec This is the period till message
about successful/unsuccessful
login appears
Page appearance 5-10 sec For text views
Refresh – page 10 sec Not including graphs
Refresh – light content (1 series – 50 observations) 5 sec Text content only
Refresh –heavy content (5 series – 100 observations) 10-15 sec Text content only
Add new content 10 sec After Finish pressed. Text content
only.
Graph content delay To be set by Additional time period needed for
PM graphic content download/refresh
Edit existing content, which belongs to the user 10 sec Period after pressing Finish on the
last Content wizard screen
Open worksheet from Available Worksheets list with To be set by
<Product>. PM
Create a task for another user – task window pop-up 5 sec? Recheck Goal Time with PM
Open an attachment of a task received 5-10 sec?
Log-out 5 sec?
Page 11 of 11

Load Software Test Plan (LSTP)

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Load Software Test Plan (LSTP)

Enviado por

Direitos autorais:

Formatos disponíveis

©2008 Doron Bar.

All Rights Reserve

Load Software Test Plan (LSTP)

File name: 9254522.doc

Name Position Date Signature Comments

Document Version Control Page

Last Modified: 18 October 2008

Document Date Author Approved Edited By Contents

2. Software Test Environment........................................................................................................................5

5. Performance goals ....................................................................................................................................11

1.3 Terminology and Acronyms

N Document Title File name (inc. path) Comments

2. Software Test Environment

2.1 Software Items

2.2 Hardware Items

2.2.1 Application Server

2.2.2 Web Server

2.2.4 WebLoad probing clients

2.3 Data environment

3. Security Management preparations:

2.4 Installation, Testing and Control

Component Machine Comments

3.1 Test Plan Strategy

The load test plan will be done in the following stages:

3.2 Load test techniques

3.2.1 Load oriented testing

3.2.2 Goals oriented

3.2.3 Stress tests

3.3 Test Execution Strategy

3.3.1 Test cycles

Process Goal time Comments

Você também pode gostar