> For the complete documentation index, see [llms.txt](https://docs.loadmill.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.loadmill.com/general/api-testing1/analyzing-an-api-test-results.md).

# Running a Test Suite

## Test Suite Run report

Once running your API Test Suite you will be directed to the Test Suite Run page. The Test Suite Run report page shows the list of executed flows as defined in the Test Suite. The Test Flows table shows **each flow's description, number of its requests, duration and status**. Use the table filter to filter the flows by their status.

In order to better analyze the results of the tests, the configuration of the Test Suite can be found right above the Test Flows table.

![](/files/-MSSKxe_VCz6q7fU3OSP)

Once you've run the Test Suite, you can re-run it by pressing the "RE-RUN" button as many times as you wish.

## Flow Status

A flow run can have the following statuses : *Pending*, *Running*, *Passed* or *Failed*.\
NOTE: In cases where a flow fails - the whole Test Suite Run will fail.

You can drill down to a specific flow and review its requests report by clicking on the relevant flow name in the table. Once clicked, you'll be directed to the Flow Report Page.

![Test Suite Flow run report page](/files/-LpSMk8WcysknbSwzWYx)


---

# 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.loadmill.com/general/api-testing1/analyzing-an-api-test-results.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.