> For the complete documentation index, see [llms.txt](https://bugowl.gitbook.io/bugowl-ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bugowl.gitbook.io/bugowl-ai/core-concepts/test-suites.md).

# Test Suites

Test Suites are collections of related test cases that can be executed together as a group. They help organize your tests by functionality, feature, or testing type.

#### What is a Test Suite?

A test suite contains:

* **Name & Description**: Clear identification of the suite's purpose
* **Type**: Category like smoke, regression, integration testing
* **Priority**: Critical, High, Medium, or Low
* **Language**: Test execution language (English, Spanish, etc.)
* **Environments**: Which environments the suite can run on
* **Test Cases**: Individual test cases belonging to the suite

#### Creating a Test Suite

1. Go to "Test Suites" → "Add New Suite"
2. Select your project
3. Enter suite name (max 100 characters)
4. Add description (max 300 characters)
5. Choose language and priority
6. Set the suite type (e.g., smoke, regression)
7. Select environments where tests will run
8. Click "Create Test Suite"

#### Test Suite Management

* **View Details**: Click the eye icon to see suite information and test cases
* **Edit Suite**: Modify name, description, type, or environments
* **Run Suite**: Execute all test cases in the suite on selected environment
* **Delete Suite**: Remove empty suites (suites with test cases cannot be deleted)

#### Suite Status

Test suites show execution status:

* **Not Run**: Never executed
* **Queued**: Waiting to run
* **Running**: Currently executing
* **Passed**: All tests completed successfully
* **Failed**: One or more tests failed
* **Canceled**: Execution was stopped


---

# 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://bugowl.gitbook.io/bugowl-ai/core-concepts/test-suites.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.