This document provides a practical guide for starting a performance testing project, highlighting key steps such as collecting non-functional requirements, identifying critical scenarios, selecting performance testing tools, and executing various test cycles. It emphasizes the importance of metrics, benchmarks, and reporting in the performance testing process. The guide also offers specific methodologies for baseline, load, stress, and endurance testing.

1. How to start Performance
Testing project?
A practical guide to performance testers
Author: NaveenKumar Namachivayam
Writer at www.QAInsights.com

2. ● Send business proposal to the
clients

3. ● Once your client agreed, start
collecting Non-Functional
Requirements

4. ● Non-Functional requirements such
as Response Time, Throughput,
Transactions per sec, CPU usage,
Memory, Disk, Network etc.

5. ● Industry standards like Response
Time < 5 seconds, CPU and
Memory usage < 60%

6. ● Identify Critical Scenarios

7. ● If your client is not able to provide
critical scenarios and workload
models, we can derive it from the
server logs.

8. ● Tools like 123loganalyzer, Deep
Log Analyzer, AWstats, Analog etc.

9. ● If no server logs available, analyze
the business applications and
identify the critical scenarios.

10. ● E.g. Banking application.
Critical Scenarios will be
1. Login
2. Check Balance
3. Apply for Loans
4. Pay Bills
...etc...

11. ● Identify the performance testing
tool

12. ● Record your critical scenarios

13. ● Enhance your scripts such as
1. Inserting Transactions
2. Correlations
3. Think Time
4. Run time settings
5. Browser settings
6. Cache settings
... etc...
then perform a unit test to baseline the
script

14. ● Create Scenarios to execute. Define
following:
1. Ramp-up period
2. Steady State
3. Ramp-down period
4. Loops
5. Mix of transactions
6. IP Spoofing
...etc...

15. ● Execute the scenario at least three cycles.
1. Baseline Test
Perform the test with 15-20% of target load
2. Load Test
Perform with actual load for three cycles.
Steady State duration: min. 1 hr
3. Stress Test
Perform load test and then slowly ramp-up the
load step-by-step. Disable Think time and Cache
settings
Steady State duration: min. 2-3 hr
4. Endurance Test
Perform load test for 10-14 hours to identify
memory leaks

16. ● Collect metrics such as
1. Response Time
2. Throughput
3. Transactions per second
4. CPU Usage
5. Memory
6. Disk utilization
● Prepare Report
● Baseline the report
● Compare with Benchmarks and previous results

17. Thank you!
Happy Performance Testing!
Visit www.QAInsights.com | www.Testifications.com |
www.QAJobOpenings.com