> 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/test-suite-editor.md).

# Test Editor

A Test Suite is a collection of Test Flows that belong to specific tasks or feature, or have some other reason to be run together. When executed, if one of the flows fails, the Test Suite run will fail.

Let's take a look at the Test Suite page.

![](/files/U8cuWOkxwEMbCqSu8wNz)

The Test Suite navigation panel includes **7 tabs**: FLOWS, LOGIN, PARAMETERS, BEFORE/AFTER, CI, COLLABORATORS and GITHUB SYNC (hidden by default).

| Tab                                                                                                     | Description                                                                                                                                                                |
| ------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| FLOWS                                                                                                   | The first and the most important tab where you write your flows.                                                                                                           |
| LOGIN                                                                                                   | Easily configure [the global login flow](https://docs.loadmill.com/api-testing/test-suite-editor/global-login-flow) that will run before each test flow of the Test Suite. |
| PARAMETERS                                                                                              | Set [default parameters](https://docs.loadmill.com/api-testing/test-suite-editor/parameters) that will be used in the Test Suite.                                          |
| [BEFORE/AFTER](https://docs.loadmill.com/api-testing/test-suite-editor/before-and-after-hooks)          | Configure a setup and teardown logic for your Test Suite.                                                                                                                  |
| [CI](https://docs.loadmill.com/integrations/npm-modal)                                                  | Integrate a Test Suite into your CI/CD process and run API tests via REST, CLI or JavaScript.                                                                              |
| [COLLABORATORS](https://docs.loadmill.com/collaboration/test-suite-collaborators-1)                     | Set team members who will be able to edit the Test Suite.                                                                                                                  |
| [GITHUB SYNC](https://docs.loadmill.com/integrations/github-integration/data-sync-connection-to-github) | Integrate Test Suite data with your GitHub repository                                                                                                                      |

####

####

####

####

####

####

####


---

# 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/test-suite-editor.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.