Lesson 1
Performance is a requirement
Without expected user volume, transaction mix and response targets, performance tests produce numbers without meaning.
All learning tracks
Core Quality EngineeringFoundation 75 min
Performance Testing Basics
Understand load, stress, soak, latency percentiles and the system evidence needed before performance testing becomes useful.
PerformanceLoadScalability
Learning outcomes
Choose the right performance test
Read percentile latency
Define workload models
Guided lessons
Learn the engineering thinking
Lesson 2
Load vs stress vs soak
Different test types answer different questions about capacity, breaking points and degradation over time.
Lesson 3
Percentiles
Average latency hides slow experiences. P95 and P99 show how the slower portion of requests behaves.
Lesson 4
Workload modelling
Represent realistic concurrency, think time and transaction distribution rather than generating arbitrary traffic.
Lesson 5
Server-side evidence
CPU, memory, database, queues and dependency timing are needed to explain why performance changes.
Hands-on practice
Do something with what you learned
Do not just tick these mentally. Write the query, create the test matrix, refactor the code, or document the decision. Practical evidence is the point.