Load Stp - Example 1
This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA
Overview
Download & View Load Stp - Example 1 as PDF for free.
More details
- Words: 1,524
- Pages: 11
©2008 Doron Bar. All Rights Reserve
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 Web QA Team Leader Head of Technical and Releases Dept. Portal development team leader Product manager
Date
Signature
Comments
Document Version Control Page File Name:
9254522.doc
Last Modified:
18 October 2008
Written By:
Document version
Date
Author
Approved
Edited By
Contents
By
Page 2 of 11 © 2008 Doron Bar All Rights Reserved – Document can be used freely only without changing this footer!!!
©2008 Doron Bar. All Rights Reserve
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, . Page 3 of 11 © 2008 Doron Bar All Rights Reserved – Document can be used freely only without changing this footer!!!
©2008 Doron Bar. All Rights Reserve
This document defines the ways of testing the application in load mode.
1.1
Purpose
The purpose of this LSTP is to define the requirements for testing. 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, 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 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
N o . (1) (2) (3)
References
Document Title
File name (inc. path)
Comments
LSTP LSTD RTM
Page 4 of 11 © 2008 Doron Bar All Rights Reserved – Document can be used freely only without changing this footer!!!
©2008 Doron Bar. All Rights Reserve
1.5
Overview 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 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.
2.1
Software Items All systems are going to run on Windows. The Web Servers are <> and <>.
2.2
Hardware Items
2.2.1
Application Server Attribute
Value
Connection
100MB
Comments
Application Server CPU Memory 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 © 2008 Doron Bar All Rights Reserved – Document can be used freely only without changing this footer!!!
©2008 Doron Bar. All Rights Reserve
2.2.3
DB server Attribut
Value
Comments
e Oracle version
Mean
Connection line
2.2.4
WebLoad probing clients Attribut
Value
Comments
e CPU Memory Operating system Connection line
2.3
Data environment
1. DB used: Oracle user
Machine
Comments
Value
Comments
2. DB characteristics: Parameter 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 © 2008 Doron Bar All Rights Reserved – Document can be used freely only without changing this footer!!!
©2008 Doron Bar. All Rights Reserve
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 Web Server + Appl. Server Load Machine Probing Client Web Load Console
Machine
Comments
Page 7 of 11 © 2008 Doron Bar All Rights Reserved – Document can be used freely only without changing this footer!!!
©2008 Doron Bar. All Rights Reserve
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
© 2008 Doron Bar All Rights Reserved – Document can be used freely only without changing this footer!!!
©2008 Doron Bar. All Rights Reserve
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 3.3.1
Test Execution Strategy 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 © 2008 Doron Bar All Rights Reserved – Document can be used freely only without changing this footer!!!
©2008 Doron Bar. All Rights Reserve
4.
Main processes This table summarizes the main processes available inside.
1. 2. 3. 4. 5. 6. 7. 8.
Process Log in Personalize content layout on Portal page Edit Tasks List view Edit Available Worksheets view Add new content Edit existing content Choose existing content from Navigation Bar Send Worksheet as a task (from Available Worksheets
9.
list) Open Worksheet withfrom the list of
10. 11. 12. 13.
Available worksheets Send a task for other Portal user Open external links from Navigation Bar Open On-Line Help Send e-mail to Portal user (by clicking on Who’s On
Comments
Line list) 14. Navigation between pages with Path Indicator 15. Log-out
Page 10 of 11 © 2008 Doron Bar All Rights Reserved – Document can be used freely only without changing this footer!!!
©2008 Doron Bar. All Rights Reserve
5.
Performance goals
This paragraph identifies the basic screen actions and the goal performance time to perform each action. For more details see also RTM. Process Log-in
Goal time 1 sec
Comments This is the period till message about successful/unsuccessful
Page appearance Refresh – page Refresh – light content (1 series – 50 observations) Refresh –heavy content (5 series – 100 observations) Add new content
5-10 sec 10 sec 5 sec 10-15 sec 10 sec
login appears For text views Not including graphs Text content only Text content only After Finish pressed. Text content
Graph content delay
To be set by
only. Additional time period needed for
Edit existing content, which belongs to the user
PM 10 sec
graphic content download/refresh Period after pressing Finish on the
Open worksheet from Available Worksheets list with
To be set by
. Create a task for another user – task window pop-up Open an attachment of a task received Log-out
PM 5 sec? 5-10 sec? 5 sec?
last Content wizard screen
Recheck Goal Time with PM
Page 11 of 11 © 2008 Doron Bar All Rights Reserved – Document can be used freely only without changing this footer!!!
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 Web QA Team Leader Head of Technical and Releases Dept. Portal development team leader Product manager
Date
Signature
Comments
Document Version Control Page File Name:
9254522.doc
Last Modified:
18 October 2008
Written By:
Document version
Date
Author
Approved
Edited By
Contents
By
Page 2 of 11 © 2008 Doron Bar All Rights Reserved – Document can be used freely only without changing this footer!!!
©2008 Doron Bar. All Rights Reserve
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
©2008 Doron Bar. All Rights Reserve
This document defines the ways of testing the
1.1
Purpose
The purpose of this LSTP is to define the requirements for testing
1.2
Scope
This document specifies the requirements for testing
Environment - hardware, software, data and installation;
-
Test strategy
-
Main
-
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
N o . (1) (2) (3)
References
Document Title
File name (inc. path)
Comments
LSTP LSTD RTM
Page 4 of 11 © 2008 Doron Bar All Rights Reserved – Document can be used freely only without changing this footer!!!
©2008 Doron Bar. All Rights Reserve
1.5
Overview
2.
Software Test Environment
This section describes software and other resources required to test the
2.1
Software Items All systems are going to run on Windows
2.2
Hardware Items
2.2.1
Application Server Attribute
Value
Connection
100MB
Comments
Application Server CPU Memory 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 © 2008 Doron Bar All Rights Reserved – Document can be used freely only without changing this footer!!!
©2008 Doron Bar. All Rights Reserve
2.2.3
DB server Attribut
Value
Comments
e Oracle version
Mean
Connection line
2.2.4
WebLoad probing clients Attribut
Value
Comments
e CPU Memory Operating system Connection line
2.3
Data environment
1. DB used: Oracle user
Machine
Comments
Value
Comments
2. DB characteristics: Parameter 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 © 2008 Doron Bar All Rights Reserved – Document can be used freely only without changing this footer!!!
©2008 Doron Bar. All Rights Reserve
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 Web Server + Appl. Server Load Machine Probing Client Web Load Console
Machine
Comments
Page 7 of 11 © 2008 Doron Bar All Rights Reserved – Document can be used freely only without changing this footer!!!
©2008 Doron Bar. All Rights Reserve
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
© 2008 Doron Bar All Rights Reserved – Document can be used freely only without changing this footer!!!
©2008 Doron Bar. All Rights Reserve
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 3.3.1
Test Execution Strategy 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 © 2008 Doron Bar All Rights Reserved – Document can be used freely only without changing this footer!!!
©2008 Doron Bar. All Rights Reserve
4.
Main processes This table summarizes the main processes available inside
1. 2. 3. 4. 5. 6. 7. 8.
Process Log in Personalize content layout on Portal page Edit Tasks List view Edit Available Worksheets view Add new content Edit existing content Choose existing content from Navigation Bar Send Worksheet as a task (from Available Worksheets
9.
list) Open Worksheet with
10. 11. 12. 13.
Available worksheets Send a task for other Portal user Open external links from Navigation Bar Open On-Line Help Send e-mail to Portal user (by clicking on Who’s On
Comments
Line list) 14. Navigation between
Page 10 of 11 © 2008 Doron Bar All Rights Reserved – Document can be used freely only without changing this footer!!!
©2008 Doron Bar. All Rights Reserve
5.
Performance goals
This paragraph identifies the basic screen actions and the goal performance time to perform each action. For more details see also
Goal time 1 sec
Comments This is the period till message about successful/unsuccessful
Page appearance Refresh – page Refresh – light content (1 series – 50 observations) Refresh –heavy content (5 series – 100 observations) Add new content
5-10 sec 10 sec 5 sec 10-15 sec 10 sec
login appears For text views Not including graphs Text content only Text content only After Finish pressed. Text content
Graph content delay
To be set by
only. Additional time period needed for
Edit existing content, which belongs to the user
PM 10 sec
graphic content download/refresh Period after pressing Finish on the
Open worksheet from Available Worksheets list with
To be set by
PM 5 sec? 5-10 sec? 5 sec?
last Content wizard screen
Recheck Goal Time with PM
Page 11 of 11 © 2008 Doron Bar All Rights Reserved – Document can be used freely only without changing this footer!!!
Related Documents
Load Stp - Example 1
November 2019 12
Load Std - Example 1
November 2019 7
Example-load-plans
December 2019 13
Lateral Load Example
October 2019 28
Stp 1
November 2019 10