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

# Run Load Test

Once a load test is created, it is automatically added to the **All Tests** list. Newly created tests appear at the **top of the list** and are ready to be executed.

{% embed url="<https://youtu.be/N4gHurnSFd4>" %}

### Step-by-Step Execution Flow

1. **Test Creation Complete**\
   After clicking **Create Load Test**, the test is saved and you are redirected to the **All Tests** screen.
2. **Initial Test Status**\
   The newly created test appears with the status **Awaiting Execution**, indicating that the test is configured but has not yet started.
3. **Start Test Execution**\
   To begin execution, click **Run Load Test** for the selected test. Before starting a load test, users can optionally provide a **Run Name** and **Run Description** to help identify the execution.&#x20;

   Both fields are **optional** and can be updated after the test execution is completed using the **“Edit icon”**. The **Run** triggers the test execution workflow.

<figure><img src="/files/2ZDQUEqAWE3saqalYA1V" alt=""><figcaption></figcaption></figure>

4. **Provisioning Progress**\
   Once the test execution is initiated, platform begins provisioning the load generators and preparing the test environment. During this process, a progress indicator is displayed which reflects the status of the provisioning and setup activities.
5. **Test Execution**\
   Once the test environment is successfully provisioned and configured, the load test execution starts automatically. The Real-Time Load Test Dashboard becomes available, enabling users to monitor execution progress and analyze performance metrics as the test runs.


---

# 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.perfagents.com/user-guide/load-test-orchestration/run-load-test.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.