> For the complete documentation index, see [llms.txt](https://docs.testvibe.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.testvibe.com/load-testing.md).

# Load Testing

Load Testing is its own section in the navigation rail, separate from functional Runs. A load test runs in one of two modes: **Simple** — concurrent browser users replay your generated feature tests and time every step — or **Advanced** — protocol-level k6 load with a configurable profile and pass/fail threshold gates, with the k6 script generated for you. Either way, the run dispatches to the cloud load fleet and charts results live.

![Load test configuration](/files/iv4BWxB4YTOLmOcoGmiO)

## What You Can Do

| Task                           | Use it for                                                                                    |
| ------------------------------ | --------------------------------------------------------------------------------------------- |
| Create a load test             | Pick journeys, a target URL, and a load profile.                                              |
| Review the generated k6 script | See exactly what will run before you start it.                                                |
| Run under load                 | Dispatch the test to the cloud load fleet with one click.                                     |
| Watch live results             | Latency percentiles, throughput, virtual users, and error rate update while the run executes. |
| Gate on thresholds             | Fail the run automatically when a latency or error-rate gate is exceeded.                     |
| Summarize or export            | Ask AI for a plain-English summary, or export JSON/CSV results.                               |
| Automate from CI or AI tools   | List and dispatch load tests over the CLI, REST API, or MCP server.                           |

## How It Relates To Functional Runs

Functional runs prove that a journey works once. Load tests replay the same journeys — alongside optional protocol-level traffic — many times in parallel to prove the application stays fast and correct under pressure. Journeys need a generated test before they can be used in a load test.

## Related Help

* [Create a load test](/load-testing/create-a-load-test.md)
* [Run a load test and read results](/load-testing/run-a-load-test-and-read-results.md)
* [Automate load tests](/load-testing/automate-load-tests.md)
* [Server telemetry](/load-testing/server-telemetry.md)
* [Run Tests](/run-tests.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.testvibe.com/load-testing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.