Performance testing
To check Speed, Scalability, stability of the product.
Types of performance testing:
1. Load Testing -
a. Check application’s ability under anticipated user load.
b. Objective: Checks performance bottleneck before product goes live.
2. Stress Testing-
a. Testing application under extreme workloads-how it handles data
processing and high traffic
b. Objective – Identify breaking points of the application.
3. Endurance Testing
a. Make sure that the application can handle the expected load for a
long period of time.
4. Spike Testing
a. Check software performance when there is sudden large spike load
generated by the users.
5. Volume Testing
a. Large number of data is populated in DB to check the software
performance.
Common performance problem
1. Long load time (long time taken to start the application)
2. Poor response time
3. Poor scalability (Software can not handle big number of users)
4. Bottlenecking (Can be rectified by code changes or Hardware chage)
a. Common bottleneck causes:
i. CPU utilization
ii. Memory utilization
iii. Network utilization
iv. Operating System limitation
v. Memory Space
Performance Testing Metrices
1. Processor Usage -amount of time processer spends executing non-idle
threads.
2. Memory use- amount of physical memory is available for to process on a
computer.
3. Disk time – amount of time disk is busy executing a read or write request.
4. Committed memory-amount of Virtual memory used.
5. Response time – Time between - from when a user enters a request and
gets the first character of response.
6. Throughput – Request received per second by a computer or network.
(Throughput expresses the amount of data that can be processed. Latency
is the time it takes for data to travel from one point to another. Network
throughput and latency together reflect a network's performance.)
7. Maximum active sessions-max number of sessions which can be active at
same time.
8. Hits per second- The number of hits per second, a server receives during
load test.
9. Thread Count-
Test Cases
1. Verify response time should not be more than 4 seconds when 1000 users
are accessing the the website simultaneously.
2. Check max number of users that an application can handle before it
crashes
3. Check DB execution time when 500 records are read/written
simultaneously.
4. Under peak load condition check:
a. CPU
b. Memory usage
c. Database server
5. Application response time under:
a. Normal load
b. Heavy load
c. Low load
d. Moderate load
JMeter
Test Plan
Test plan consist of all actions and components that we need to execute our
performance test script.
Workbench
It is taken as practice area/temporary storage as the components of workbench
not get saved along with Test Plan. A most important component in
HTTPSTestScriptRecorder which can record the script directly and tester can put
the load on those later on.
JMeter Components
1. Thread Group – represents users.
2. Samplers- Type of request (HTTP, FTP etc.)
3. Listener – Used to check the Test result/Report -How result look like using
different metrics.
4. Config Element- To set configuration for the test- some cookies, header,
JDBC connection, Random variables etc.
5. Assertion – Used for putting validation.
6. Timer – Used to set delays/wait between the tests.
7. Pre Processor – Used when we want to run some script/tweak some HTML
link/load some environment variable in our test for data driven test, before
executing test.
8. Post Processor – It run after execution for retrieve the response.
JMeter Test Steps
1. Create Test Plan
2. Create Thread Group (Users)
3. Add Sample (HTTP)
4. Add Listener
5. Run Test Plan
6. Save Test Plan
Thread group properties:
1. Name
2. Number of Threads – No. of user
3. Ramp up period(in seconds) – Duration/gap between two users will
send the request. If there are 3 users and ramp up time is 4 seconds
then: First user will send the request -> after 4 seconds Second user
will send the request -> after 4 second Third user will send the request
and so on.
4. Loop count – put number how many times user can send the request
5. Forever – If we check this checkbox then users will keep sending the
request.
Sampler properties:
1. Protocol
2. Server name/IP
3. Path – Only put / if does not want to specify anything otherwise example
/index(to open the index page.
4. Port
5. Method
Example report-Tree View
Thread Name:Users 1-1
Sample Start:2025-05-22 12:14:13 IST
Load time:573
Connect Time:99
Latency:537
Size in bytes:20622
Sent bytes:112
Headers size in bytes:1083
Body size in bytes:19539
Sample Count:1
Error Count:0
Data type ("text"|"bin"|""):text
Response code:200
Response message:OK
HTTPSampleResult fields:
ContentType: text/html; charset=ISO-8859-1
DataEncoding: ISO-8859-1
==================Udemy course topics===========
1. Thread Group(1 hr)
2. Listener
3. Result Tree
4. Assertion (26m)
5. Timers
6. Data Driven Testing (40m)
7. Regular Expressions (23m)