What is Stress Testing?

Stress testing pushes a system beyond its expected capacity to find its breaking point and observe how it fails and recovers under extreme load.

Start a Free Mock Interview

Free to start · 7-day trial on paid plans

IN DEPTH

In depth.

Where load testing verifies behavior at expected and peak traffic, stress testing deliberately exceeds those limits. The goal is not a pass/fail at a target throughput but understanding the failure mode: at what concurrency does latency spike, where do errors begin, which resource (CPU, memory, DB connections, thread pools) saturates first, and does the system degrade gracefully or fall over.

A crucial and often-overlooked part of stress testing is recovery: once load is removed, does the system return to normal, or does it stay degraded (memory leaks, stuck queues, exhausted connection pools)? Related variants include spike testing (sudden sharp load increases), soak/endurance testing (sustained load over hours to surface leaks), and breakpoint testing (gradually ramping until failure to find the exact ceiling).

Tools like k6, JMeter, Gatling, and Locust drive the load, while observability (metrics, traces, logs) is what makes the results actionable. Without monitoring the system under test, a stress test only tells you that it broke, not why.

WHY IT MATTERS

Why interviewers ask about this.

Interviewers ask about stress testing to see whether you understand non-functional requirements and can reason about failure modes and capacity, not just functional correctness, a key signal for SDET and performance roles.

EXAMPLE

Example scenario.

Before a product launch, a team ramps virtual users in k6 well past projected peak. At 3x expected traffic, database connection pool exhaustion causes cascading timeouts, and the service does not recover after load drops because connections stay leaked. They add pool limits, timeouts, and a circuit breaker, then re-test to confirm graceful degradation and recovery.

TIP

Interview tip.

Clearly distinguish stress testing from load testing, and mention recovery behavior plus related types (spike, soak, breakpoint). Tying results to a specific saturated resource shows real performance-testing experience.

FAQ

Frequently asked questions.

What is the difference between stress testing and load testing?

Load testing checks behavior at expected and peak traffic against targets. Stress testing deliberately exceeds capacity to find the breaking point and observe failure and recovery behavior.

What is soak testing?

Soak (endurance) testing applies sustained load over a long period to surface slow problems like memory leaks, log growth, or connection pool exhaustion that short tests miss.