1/17
1 load testing quiz
Name | Mastery | Learn | Test | Matching | Spaced | Call with Kai | Chat |
|---|
No analytics yet
Send a link to your students to track their progress
Software Testing
is a process of evaluating a software application to determine whether it behaves according to its requirements and to identify defects, errors, or unexpected behavior.
Functional testing
evaluates what the system does. it checks whether individual features and functions behave according to requirements
Non-functional testing
evaluates how well the system operates. instead of focusing solely on individual features it examines characteristics
Performance
refers to how efficiently and effectively a system responds to workloads and user request
Performance testing
is a type of non-functional software testing used to determine how a system behaves in terms of speed, responsiveness., stability, scalability and resource utilization under a particular workload.
Load testing
is performance evaluation technique where we simulate the expected number of users or transactions on a system to measure its responsiveness, stability, and overall behavior.
Concurrent users
are users interacting with a system during the same period.
It identifies performance problems before deployment.
a system may work perfectly during development because only one or two developers are using it.
It identifies bottleneck
is a component that limits overall system performance
It improves user experience
users expect responsive systems
It supports scalability planning
testing helps developers understand whether their architecture can supporting increasing workloads.
Slow response time
pages or functions take too long
Timeouts
the application takes so long that the request expires
Server errors
under heavy traffic, users may encounter
Application crash
the application may stop responding completely
High resource utilization
this may indicate that the system is approaching resource limits
Database
slow queries, missing indexes, excessive database requests, too many simultaneous connections, poor database design
Performance degradation
user 10 = 0.8sec, users 50 = 1.2sec, users 100 = 2.1sec, users 200 = 5.8sec, users 300 = 14.5sec