Skip to main content
Specialized Testing

What Is Load Testing?

Load testing is the practice of simulating expected or peak user traffic against a system to verify that it meets performance requirements (response time, throughput, error rate) under realistic load conditions.

Start a Free Mock Interview

Free to start · 7-day trial on paid plans

In Depth

Load testing answers the question: "Can the system handle the traffic we expect?" Related but distinct types include stress testing (pushing beyond expected load to find the breaking point), spike testing (sudden traffic surges), soak testing (sustained load over hours to find memory leaks), and capacity testing (determining the maximum supported throughput).

A load test scenario defines virtual users (VUs), each simulating a realistic user journey with think times between actions. For example, 500 VUs might concurrently: log in, search for a product, add to cart, and check out. The test measures response times (average, p95, p99), throughput (requests per second), error rate, and server resource utilization (CPU, memory, database connections).

Tools like k6 (scriptable in JavaScript, developer-friendly), JMeter (UI-based, widely adopted), Gatling (Scala-based, good for CI), and Locust (Python-based) enable load test automation. The key to useful load testing is realistic scenarios, not just hammering a single endpoint. Include multiple user journeys, realistic data, and appropriate think times.

Why Interviewers Ask About This

Interviewers ask about load testing for roles that touch performance or infrastructure. Understanding load testing shows you think about non-functional requirements, not just features.

Example Scenario

Before Black Friday, a retail team runs a load test with 10,000 concurrent users simulating browse-search-buy journeys. At 7,000 VUs, p95 response time exceeds the 3-second SLA. Profiling reveals a database query missing an index. After adding the index, the system handles 12,000 VUs within SLA.

Interview Tip

Distinguish between load, stress, spike, and soak testing. Name specific tools and discuss what metrics you monitor. Describe a load test you have designed, including how you defined realistic scenarios.

Related Terms

Explore related glossary terms to deepen your understanding.

Performance BudgetA performance budget is a set of measurable limits on web performance metrics (such as page load time, bundle size, or Core Web Vitals) that a team commits to not exceeding, enforced through automated checks.
Chaos EngineeringChaos engineering is the discipline of deliberately injecting controlled failures into a system in production or pre-production to proactively discover weaknesses before they cause unplanned outages.
ObservabilityObservability is the ability to understand the internal state of a system from its external outputs, primarily through three pillars: structured logs, metrics (time-series data), and distributed traces.
Test EnvironmentA test environment is the configured infrastructure (servers, databases, services, and network settings) where tests are executed, designed to simulate production conditions at the appropriate fidelity for each testing level.
Continuous TestingContinuous testing is the practice of executing automated tests at every stage of the CI/CD pipeline, providing immediate feedback on the risk level of each code change as it moves toward production.

Related Resources

Dive deeper with these related interview prep pages.

k6 Interview QuestionsJMeter Interview QuestionsGatling Interview QuestionsSDET Interview Prep

Ready to Ace Your QA Interview?

Practice explaining load testing and other key concepts with our AI interviewer.

Join 1,200+ QA engineers already practicing with AssertHired.

Start Your Free QA Interview

Free to start · 7-day trial on paid plans

Written by Aston Cook, Senior QA EngineerLast updated: March 2026