> For the complete documentation index, see [llms.txt](https://docs.walnutai.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.walnutai.ai/test-and-quality-management/test-management/test-suites/creating-and-adding-test-cases-to-a-suite.md).
# Creating and Adding Test Cases to a Suite
#### **Steps to Create a Suite**
* **Navigate to Suites:** Go to the Test Cases module and click the **'Suites'** tab located next to it.
* **Initialize:** Click Create **'Suite'**.
* **Define Details:**
* Suite Name: Provide a unique, descriptive label.
* Description: Add context regarding the suite's purpose.
* **Status:** Switch between Active and Inactive.
{% hint style="info" %}
A suite can only be executed when its status is set to Active. If the status is Inactive, the execution button is disabled.
{% endhint %}
* **Save:** Click **'Create Suite'** to finalize.
#### **Steps to Add Test Cases to a Suite**
* Choose the desired test suite where you want to include test cases
* Browse the project’s test case list from the left-hand panel. Select the required test cases and click **'Add Selected'** to include them in the suite or simply drag test cases from the project list and drop them directly into the suite for quick organization.
---
# 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.walnutai.ai/test-and-quality-management/test-management/test-suites/creating-and-adding-test-cases-to-a-suite.md?ask=&goal=
```
`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.