This document provides a test script description for load and performance testing of mobile applications. It outlines clients and scenarios to be tested, protocols and services used, expected data and criteria, minimum system requirements, and detailed descriptions of test scenarios including steps, validations, and expected responses.

1. www.ginsbourg.com
Performance & Load Test
Test Script Description
Customer: Company Name
Project: Mobile Applications
Edited by: Shay Ginsbourg
Revision: 1.2
Date: 11-May-2014

2. www.ginsbourg.com
Page 2 of 12
Document Version History
Revision Date Author Details
1.0 01.05.14 Shay Ginsbourg Document established.
1.1 10.05.14 Shay Ginsbourg Glossary and Abbreviations added.
1.2 11.05.14 Shay Ginsbourg Clients & Scenarios added.
Protocols & Services added.
Data & Criteria added.
Minimum OS and Hardware Requirements added.

3. www.ginsbourg.com
Page 3 of 12
Contents
1. Scope .................................................................................................................. 4
2. Introduction.......................................................................................................... 4
A. General............................................................................................................. 4
B. Clients & Scenarios .......................................................................................... 4
C. Protocols & Services ........................................................................................ 5
D. Data & Criteria.................................................................................................. 5
3. Minimum OS and Hardware Requirements ......................................................... 7
4. Glossary and Abbreviations................................................................................. 8
5. Scenario Descriptions.......................................................................................... 9
4.1. Scenario for Login and browsing................................................................... 9
4.2. Scenario for TBD 1...................................................................................... 10
4.3. Scenario for TBD 2...................................................................................... 10
4.4. Scenario for TBD 3...................................................................................... 11
4.5. Scenario for TBD 4...................................................................................... 12

4. www.ginsbourg.com
Page 4 of 12
1. Scope
This document provides a specified description of the test scripts intended for a web
performance and load test. The document provides all the required information on
the clients & scenarios, the protocols & services, the data & criteria, the minimum OS
and hardware requirements, the relevant glossary and abbreviations list, and finally,
the full scenario descriptions.
2. Introduction
A. General
2.1.The public URL of the web site/application under test is:
___________________________
2.2.The types of web servers and database servers that operate the web
site/application are: ___________________________
2.3.The development tools that were used for developing the web site/application
are: ___________________________
B. Clients & Scenarios
2.4.The types of desktop and mobile clients that would request that URL are:
___________________________
2.5.MS-IE browser can/can’t access the web site/application under test.
2.6.The web site/application is/isn’t designed for clients other than MS-IE
browser. They are: ___________________________

5. www.ginsbourg.com
Page 5 of 12
2.7.The number of users that are expected to concurrently access it (running at
the same time) is: ___________________________
2.8.The common operations that users are expected to perform at that web site
are: ___________________________
2.9.The number of scenarios that are needed to be tested under load are:
___________________________
2.10. Extensive functional testing was/wasn’t successfully passed for the
above specified scenarios. The functional testing conclusions were:
___________________________
C. Protocols & Services
2.11. The clients communicate with the server by GET/POST methods of
HTTP protocol. TRUE / FALSE ___________________________
2.12. The server communicates with the client by sending HTTP responses.
TRUE / FALSE ___________________________
2.13. The connection between the client and the server secured by HTTPS
protocol. TRUE / FALSE ___________________________
2.14. The user have to login into the website by using a private password:
TRUE / FALSE ___________________________
2.15. The client and server communicate in methods of protocols other than
HTTP/HTTPS. TRUE / FALSE ___________________________
2.16. The server application provides Web services as follows: (SOAP,
REST, WCF, etc.) ___________________________
D. Data & Criteria
2.17. The number of kilo bytes of data that the server sends to the client
every second on average is: ___________________________

6. www.ginsbourg.com
Page 6 of 12
2.18. The number of kilo bytes of data does that clients send to the server
every second on average is: ___________________________
2.19. The entrance criteria to the load test (initial database, load generation
hardware, etc.) are: ___________________________
2.20. The exit criteria from the load test (Average response time, throughput,
etc.) are: ___________________________

7. www.ginsbourg.com
Page 7 of 12
3. Minimum OS and Hardware Requirements
The minimum hardware requirements for each load generation host are:
CPU i5
RAM 4 GB
HD/SSD 500 GB
Ethernet 1 GB
For UNIX hosts (RECOMENDED), the specific additional requirements are:
OS Desktop Linux Ubuntu 14 64-bit
Java Java virtual machine 64-bit for UNIX
Web Internet access
For Windows hosts, the specific additional requirements are:
OS Desktop Microsoft Windows 7 64-bit
Java Java virtual machine 64-bit for Window
Sniffer Fiddler 4 for Windows
Web Internet access

8. www.ginsbourg.com
Page 8 of 12
4. Glossary and Abbreviations
AJAX Asynchronous JavaScript and XML
ALM Application Life Management
ASP Active Server Pages
CRM
Customer Relationship
Management
ERP Enterprise Resource Planning
FTP File Transfer Protocol
GUI Graphic User Interface
GWT Google Web Toolkit
HTTP Hypertext Transfer Protocol
HTML Hypertext Markup Language
IDE
Integrated Development
Environment
IMAP Internet Message Access Protocol
iOS Apple Mobile Operating System
IP Internet Protocol
J2EE Java 2 Platform Enterprise Edition
LR LoadRunner
N/A Not Available
NCA Network Computing Architecture
NTLM
Windows NT LAN Network
Manager
NV Network Virtualization
OS Operating System
POP3 Post Office Protocol version 3
RTE Remote Terminal Emulation
RUM Real User Monitoring
SaaS Software as a Service
SMP SAP Mobile Platform
SMTP Simple Mail Transfer Protocol
SNMP
Simple Network Management
Protocol
SOA Service-Oriented Architecture
SPA Single Page Applications
SQL Structured Query Language
UI User Interface

9. www.ginsbourg.com
Page 9 of 12
5. Scenario Descriptions
4.1. Scenario for Login and browsing
Step Description Validation
1 Start at URL: TBD Verify response time < 4 sec
2 Enter user and password and click OK. Verify entering the app by finding
string “HELLO” in the HTML.
3 Go to TBD Verify that size of FLASH is > 5 MB
4 Verify REGEX: TBD
5
6
7
8
9
10

10. www.ginsbourg.com
Page 10 of 12
4.2. Scenario for TBD 1
Step Description Validation
1
2
3
4
5
6
7
8
9
10
4.3. Scenario for TBD 2
Step Description Validation
1
2
3
4
5

11. www.ginsbourg.com
Page 11 of 12
Step Description Validation
6
7
8
9
10
4.4. Scenario for TBD 3
Step Description Validation
1
2
3
4
5
6
7
8
9
10

12. www.ginsbourg.com
Page 12 of 12
4.5. Scenario for TBD 4
Step Description Validation
1
2
3
4
5
6
7
8
9
10