> For the complete documentation index, see [llms.txt](https://mozarkdocs.gitbook.io/appx_documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mozarkdocs.gitbook.io/appx_documentation/test-context-manager-documentation/test-cases/creating-a-test-case/organizing-with-folders.md).
# Organizing with folders
## Organizing with folders
Folders let you group test cases in a navigable hierarchy.
Use folders to keep large repositories structured.
### Create a folder
1. Open the **Test Cases** page.
2. Click the folder icon or **New Folder**.
3. Enter the folder details.
4. Save the folder.
### Move test cases into a folder
1. Select one or more test cases with the checkboxes.
2. Click **Move to Folder**.
3. Choose the target folder.
### Navigate folders
The folder tree appears in the left panel of the **Test Cases** page.
Click a folder to filter the list.
### Rename or delete a folder
Right-click a folder in the tree to rename or delete it.
{% hint style="info" %}
Deleting a folder does not delete its test cases. Test Manager moves them to the root level.
{% endhint %}
---
# 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://mozarkdocs.gitbook.io/appx_documentation/test-context-manager-documentation/test-cases/creating-a-test-case/organizing-with-folders.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.