3.5.

3 Performance Testing

To ensure the system performs under expected load, performance testing will be conducted. This
includes testing the system's response time, throughput, and scalability when multiple users
access it simultaneously. The performance test metrics will be your baseline to conduct the
performance testing by using the test case template provided in the Appendix G. Attach the
created form in Appendix G. Attached documentation (pictures) during the conduct of the testing
in APPENDIX L.
 APPENDIX G

Manual Testing Form for Performance Testing

Performance Metrics

Test Metric Metric Expected Observed Pass/Fail Remarks

Definition Value Value

Response Time taken ≤2s 1.8s Pass The system

Time for the responds
system to quite swiftly
respond to to user
user actions actions.
(in seconds)

System Number of ≥15 TPS 6 TPS Pass Anything

Throughput transactions above 20
processed per TPS is
second considered
bad, so the
Current
transaction
s per
second are
considerabl
y good

Error Rate Percentage of ≤1% 0% Pass No errors

failed occurred
transactions during the
user
interaction
phase
CPU Usage Percentage of ≤50% 6% Pass The
CPU usage application
during test whether in
an active or
passive
state is at
an
optimized
enough
state to not
eat a high
amount of
resources.

Memory Percentage of ≤70% 9% Pass The

Usage memory resource
usage during managemen
test t is
considerabl
y good.

System Number of ≤5 1 Pass No

Errors errors significant
Logged encountered or severe
(e.g., 404 errors
errors, server occurred
downtime) during the
testing,
only simple
quality of
life errors
occurred
like the
back button
not having
an action
tied to it.
Test Case Template - Performance Testing

Test Scenario Multiple users Test

are interacting Case
with the system. ID 001

Test Case Description Simulating user interaction with the system during peak usage
(multiple users simultaneously accessing key functionalities like
login, data retrieval, and submission).

Test Objective To evaluate the system's performance when multiple users interact
simultaneously, focusing on response time, system stability, and
resource utilization.

Test Configuration

No. of 6
Simultaneous
Users:

User actions simulated:

Login to the system

Data retrieval (e.g., search, filtering)

Data submission (e.g., form submissions)

Navigation through different pages

 System Resources to be monitored:

CPU Usage

Memory Usage

Network Bandwidth

Disk I/O

Test Execution Steps:

S.No Action Inputs / Expected Value Actual Pass/Fail Remarks

Coverage / Output Result
Path

1 Initialize Set up load Environment No errors Pass Environment

Performance testing tool ready, no errors present used for
Test with N users testing
Environment remained
stable

2 Start Simultaneous All users Users log Pass Memory

Concurrent login attempts successfully log in with during
User Sessions by N users in within appropria concurrent
acceptable te user sessions
response time response significantly
(e.g., < 2s) time increase load
(<3s) in but not
presence enough to
of good impede usage
internet
 connectiv
ity

3 Simulate Data Each user Search results Fast Pass Database

Retrieval performs returned within database queries were
(Search/Filter) search queries acceptable time query, recorded to
concurrently (e.g., < 3s) fast function as
search intended
action

4 Simulate Data Each user Successful form Successf Pass Database

Submission submits forms submissions ul form write options
concurrently logged in DB, submissi work as
(e.g., 50% of response time < ons, intended
them) 2.5s forms
documen
ted in
firebase
database

5 Users Navigate Users click Pages load Fast load Pass Network and
Through Pages through within times for Disk input
various pages acceptable each of and output
(pagination) times (e.g., < applicati work as
2s/page) ons intended and
frames there is not
much delay

6 Sustained Load Maintain N System remains Stable, Pass Application

for Defined users stable, no did not appropriately
Duration (e.g., performing crashes, slow uses resources
30 mins) mixed actions minimal error down such that it
rates (< 1%), does not
 stable resource hinder devices
usage much

7 Gradually Increase users System may Search Pass Phone

Increase User beyond degrade and hardware is to
Count (Stress expected peak gracefully, actions be taken
Test) (N+X) response times requiring account of,
increase validatio older models
predictably, no n take a tend to slow
unexpected bit longer down quicker
failures compared to
more
optimized
newer devices

8 Collect CPU, Resource usage Applicati Pass Resource

Performance Memory, within on does saturation is
Metrics Network, Disk acceptable not balanced
I/O monitoring thresholds significa
(CPU < 80%, ntly
Memory < degrade
75%) device
performa
nce
 APPENDIX L.

Stress Testing with Multiple Users for Extended Time Periods: