# Load Test

## Introduction

* Many things can go wrong when a system is under load. The system must run numerous operations simultaneously and respond to different requests from a variable number of users. To prepare for these performance risks, teams use load testing.



## Types

![](https://1374779285-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MFW3x2aqEO8GF2kr3VU%2Fuploads%2FWXmxeFNbNHh1xAks7oac%2Fimage.png?alt=media\&token=a907e579-5b7f-4b00-ad61-21180dca94e1)

* [**Smoke tests**](https://k6.io/docs/test-types/smoke-testing) validate that your script works and that the system performs adequately under minimal load.
* [**Average-load test**](https://k6.io/docs/test-types/load-testing) assess how your system performs under expected normal conditions.
* [**Stress tests**](https://k6.io/docs/test-types/stress-testing) assess how a system performs at its limits when load exceeds the expected average.
* [**Soak tests**](https://k6.io/docs/test-types/soak-testing) assess the reliability and performance of your system over extended periods.
* [**Spike tests**](https://k6.io/docs/test-types/spike-testing) validate the behavior and survival of your system in cases of sudden, short, and massive increases in activity.
* [**Breakpoint tests**](https://k6.io/docs/test-types/breakpoint-testing) gradually increase load to identify the capacity limits of the system.

## Reference

{% embed url="https://k6.io/docs/test-types/load-test-types/" %}

\
