"Performance testing" covers several distinct test types, each answering a different question about how the system behaves under pressure. Load and stress testing are the most common; endurance and volume testing cover longer-term and data-heavy concerns.
The most common types
Load Testing
Checks behaviour under expected load.
- Simulates realistic, anticipated user numbers.
- Confirms the system meets its targets.
- The most common performance test.
Stress Testing
Pushes beyond normal limits.
- Increases load until the system struggles or breaks.
- Finds the breaking point and how it fails.
- Checks whether it recovers gracefully.
Other important types
- Endurance (soak) testing — sustained load over a long period to reveal slow problems like memory leaks or gradual slowdown.
- Volume testing — large volumes of data to check how the system copes as databases and files grow.
- Spike testing — sudden sharp increases in load to see how the system handles bursts.
- Scalability testing — how well the system improves when resources are added.
In practice: most engagements begin with load and stress testing, then add endurance and volume where the risk justifies it — for example, a system that runs for weeks between restarts needs endurance testing.
Conclusion
Load and stress testing answer the everyday performance questions — "can it handle expected traffic?" and "where does it break?" — while endurance and volume testing guard against slow-burning and data-growth problems. Choosing the right mix depends on how your system is actually used.