2. Introduction to Performance Testing.
Load Testing.
Difference between Performance, Load
Testing.
Why Performance Testing.
When is it required?
Process of Testing.
Testing Tools.
SHW 2
3. It is a process of determining the speed or
effectiveness of a computer, network,
software program or device.
Factors of Performance testing:
Response Time
Throughput
Capacity
Stability
SHW 3
4. It is defined as the delay between the point
of request and the first response from the
product.
It Increases proportionally to the user load.
SHW 4
5. Ability to handle multiple transactions in a
given period.
When the number of users increase, the
throughput almost increase with the number
of requests.
SHW 5
6. Test behavior of the software under load and
peak conditions.
Eg:
Testing a word processor in a very large document.
Running multiple applications simultaneously.
SHW 6
7. Identifies problems early on before they
become costly to resolve
Develop more quality and scalable product.
To make sure the product meets response
time, throughput etc..
SHW 7
8. It can be started from the requirements gathering phase and
continue until deployment phase of the software for reduce the
cost and time to rework.
Planning and Design Phase
Identify the best configuration for software when there are
accessing thousands of users.
Development Phase
Detect breaking points, unnecessary codes and bottlenecks
in the software.
Deployment Phase
To check the minimum requirements (Hardware / Software)
for the application are to runs it properly.
Maintenance Phase
Identifying reasons/ factors which effect for degrade the
performance of the software.
SHW 8
10. Identify the Test Environment
Identifies the Environment including hardware,
software and network configurations. This process
will help to testers for create more effective tests.
Identify Performance Acceptance Criteria
It’s very important when initiate early in the
application’s development life cycle and it records
the acceptance criteria of the application.
SHW 10
11. Plan and Design Tests
It defines roles and responsibilities, test schedule,
test environment preparations, etc….
Test Design is about type of test to be conducted,
metric to be measured, metadata, scripts, etc…
SHW 11
12. Configure the Test Environment
Do the preparations for the testing environment.
Arrange tools and other resources.
Implement the Test Design
Construct the performance test by following on test
design.
Execute the Test
Do the execution and monitor tests.
SHW 12
13. Analyze Results, Report, and Retest
collect the output of monitoring and converts them into
one format.
There are two types of reports,
1. First report includes graphic and basic information.
2. Second report includes profound information and statics
about the system.
Retest and check whether there is an improvement or
decrement of the performance.
SHW 13
15. 100% Java desktop application.
For web and FTP, Java, SOAP/XML-RPC, JDBC
applications
Advantages:
Open Source
Various target systems.
Extensibility.
Drawbacks:
Necessary to start remote machine one by one.
SHW 15
16. Works on Windows, Mac, Linux, AIX platforms.
Support to Citrix, Socket Recording, Web HTTP,
SOA, SAP protocols.
Advantages:
Support XML
No programming knowledge required.
Run with large multi users tests.
Drawbacks:
Java Applet based applications not supported.
Scheduling is not possible.
SHW 16