Load Software Test Description (LSTD)

©2008 Doron Bar.
All Rights Reserved
<Product>
<Version>
Load Software Test Description (LSTD)

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

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

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

version By
Page 2 of 10
Table of Contents
1. Introduction.................................................................................................................................................4
1.1 Purpose......................................................................................................................................................4
1.2 Scope..........................................................................................................................................................4
1.3 Terminology and Acronyms.....................................................................................................................4
1.4 References..................................................................................................................................................4
2. User profiles.................................................................................................................................................5
2.1 Profile 1 – Simple Login...........................................................................................................................5
2.2 Profile 2 –Edit Content.............................................................................................................................5
2.3 Profile 3 – Create Tasks............................................................................................................................5
2.4 Profile 4 – Receive Tasks..........................................................................................................................5
2.5 Profile 5 – Add New Content, e-Mail, Help............................................................................................7
3. Load size and distribution.........................................................................................................................8

3.1 Browser distribution.................................................................................................................................8
3.2 Profiles distribution..................................................................................................................................8
3.3 Load size levels..........................................................................................................................................8
4. Other issues.................................................................................................................................................9
4.1 Profiles synchronization...........................................................................................................................9
4.2 Re-running of the profiles........................................................................................................................9
4.3 Running one profile simultaneously for different users......................................................................10
10
Page 3 of 10
1. Introduction
This document serves as the Load Software Test Description for the <Product>, <Version>.
This document defines the ways of testing the <Product> application in load mode
1.1 Purpose
The purpose of this LSTD is to present the load software test description will include the following topics:
• Common user profiles
• Load size and distribution
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.
LSTD describes user profiles that will be used for recording and editing test Agendas for load tests. It also
describes load size for each of load levels (low, medium, high) and share of each profile (agenda) in overall
load created during the test.
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 10
2. User profiles
2.1 Profile 1 – Simple Login

Process Comments
1. Login: invalid username
2. Login: invalid password
3. Login
4. Personalize Portal user page
5. Choose existing content from Navigation Bar
6. Choose My Home Page (My Portal) on Path Indicator
7. Log-out
2.2 Profile 2 –Edit Content

Process Comments
1. Login
2. Edit existing content
4. Personalize Portal user page
5. Edit existing content
6. Choose existing content from Navigation Bar
8. Sleep - remain idle till automatic logout Check session timeout settings
2.3 Profile 3 – Create Tasks

Process Comments
1. Login
2. Personalize Tasks List view
3. Create task for user of profile 4
4. Open external link from Navigation Bar
5. Send worksheet as task to Profile 4
6. Log-out
2.4 Profile 4 – Receive Tasks

Process Comments
Page 5 of 10
1. Login
2. Personalize Tasks List view
3. Refresh Tasks List – Check for tasks received from Profile 3
4. Open a task (by clicking on it in Tasks List)
5. Mark a task as ‘Done’
6. Refresh Tasks List
7. Personalize Available Worksheets list
8. Open worksheet – B2B Partner
9. Open received from Profile 4 task – Partner worksheet
10. Log-out
Page 6 of 10
2.5 Profile 5 – Add New Content, e-Mail, Help

Process Comments
1. Login
2. Send e-mail to Portal user by clicking on its name in Who’s May be problematic to test,
On Line window because Who’s On Line
window is applet, and e-mail
opens by Outlook. We can
record only HTTP
transactions in Web Load
3. Open On-line Help
4. Close On-line Help
5. Add new content
6. Log-out
Page 7 of 10
3. Load size and distribution
3.1 Browser distribution

All tests will be executed using IE<n> browser emulation.
3.2 Profiles distribution

Profile % Comments
number distribution
Profile 10
1
Profile 20
2
Profile 30
3
Profile 30
4
Profile 10
5
3.3 Load size levels

Load Number of virtual Comments
level clients
Low 5
Medium 50
High 10
0
Page 8 of 10
4. Other issues
4.1 Profiles synchronization

We can synchronize profiles (Web Load agendas) while running tests:
1) First profile sends a task to second profile, and the second profile checks if the task was received. During the
test run, the profile that receives the tasks will be run only after the profile that sends the tasks have been
accomplished.
2) A user from one profile updates public content, and users with other profiles see the changes. This functional
test is not necessary, since our main goal is load testing, but this check could simulate real-world conditions
during the tests. We shall postpone this issue for the future.
4.2 Re-running of the profiles

During load tests we will try to re-run the same profiles several times in order to check the stability of the
application during a long time period.
How can we re-run several times the profile (agenda) that creates a new content (say content named Graph1)
each time? The content will be created during the first run, and during the second run of the profile the script
will attempt to create a new content with the same name. This can cause to the errors during load session.
The similar problem appears while re-running the profile that personalizes contents layout on Portal page. I
Possible solutions:
Solution Disadvantages
1. Run profiles which makes changes of contents or We can not run long load tests using these profiles
changes of contents layout in Portal only once.
2. Read the name of a newly created content from During a long load tests a large number of new
external file during each profile run read. Thus contents contents will be created. This could worsen the
like Graph1, Graph2, etc. will be created performance and create unusual stress conditions.
3. Run profiles which make changes of contents or
changes of contents layout in Portal limited number of
rounds. Names for new contents will be read from
external file (as in solution 2).
The best solution, on our opinion, is 3. Profile that creates a new content will be run for a limited number of
rounds during the test run. Profiles that edit existing content will be run repeatedly along the whole test run.
Page 9 of 10
This profile will not actually change the settings of the existing content, but only move between the screens of
Edit Content wizard.
4.3 Running one profile simultaneously for different users

Profile (Web Load agenda) could be run simultaneously for a number of Virtual Clients.
Each Virtual Client emulates separate Portal user, which acts in accordance with the steps
specified for the profile he belongs to.
If we define single user name and password for a profile, then simultaneous run of this
profile will lead to the “User is already logged in” message. In order to resolve this
problem, the external file containing user names and passwords will be created. Web Load
will read this data from the file, assigning different user names and passwords for each of
Virtual Clients.
Page 10 of 10

Load Software Test Description (LSTD)

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Load Software Test Description (LSTD)

Uploaded by

Copyright:

Available Formats

©2008 Doron Bar.

All Rights Reserved

Load Software Test Description (LSTD)

File name: 9510045.doc

Name Position Date Signature Comments

Document Version Control Page

Last Modified: 22 October 2008

Document Date Author Approved Edited By Contents

3. Load size and distribution.........................................................................................................................8

1.3 Terminology and Acronyms

N Document Title File name (inc. path) Comments

2.1 Profile 1 – Simple Login

2.2 Profile 2 –Edit Content

2.3 Profile 3 – Create Tasks

2.4 Profile 4 – Receive Tasks

2.5 Profile 5 – Add New Content, e-Mail, Help

3. Load size and distribution

3.1 Browser distribution

3.2 Profiles distribution

3.3 Load size levels

4.1 Profiles synchronization

4.2 Re-running of the profiles

4.3 Running one profile simultaneously for different users

You might also like