LOAD TESTING QUIZ

0.0(0)
Studied by 3 people
call kaiCall Kai
Locked
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/17

flashcard set

Earn XP

Description and Tags

1 load testing quiz

Last updated 1:58 PM on 8/13/26
Name
Mastery
Learn
Test
Matching
Spaced
Call with Kai
Chat

No analytics yet

Send a link to your students to track their progress

18 Terms

1
New cards

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.

2
New cards

Functional testing

evaluates what the system does. it checks whether individual features and functions behave according to requirements

3
New cards

Non-functional testing

evaluates how well the system operates. instead of focusing solely on individual features it examines characteristics

4
New cards

Performance

refers to how efficiently and effectively a system responds to workloads and user request

5
New cards

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.

6
New cards

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.

7
New cards

Concurrent users

are users interacting with a system during the same period.

8
New cards

It identifies performance problems before deployment.

a system may work perfectly during development because only one or two developers are using it.

9
New cards

It identifies bottleneck

is a component that limits overall system performance

10
New cards

It improves user experience

users expect responsive systems

11
New cards

It supports scalability planning

testing helps developers understand whether their architecture can supporting increasing workloads.

12
New cards

Slow response time

pages or functions take too long

13
New cards

Timeouts

the application takes so long that the request expires

14
New cards

Server errors

under heavy traffic, users may encounter

15
New cards

Application crash

the application may stop responding completely

16
New cards

High resource utilization

this may indicate that the system is approaching resource limits

17
New cards

Database

slow queries, missing indexes, excessive database requests, too many simultaneous connections, poor database design

18
New cards

Performance degradation

user 10 = 0.8sec, users 50 = 1.2sec, users 100 = 2.1sec, users 200 = 5.8sec, users 300 = 14.5sec