> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/create-and-execute-tests-with-design-studio/working-with-test-case-section/features-in-test-case-section-1/tag-test-case.md).

# Tagging Test Case

The Tags feature helps you categorize and organize test cases using keywords. Tags make it easier to identify related test cases and quickly filter or select them when creating execution configurations or searching for test cases. This article explains how to add tags to a test case.

{% hint style="info" %}
**Note:** You can assign multiple tags into a test case.
{% endhint %}

To tag a test case, perform the following actions:

1. On the **Home** page, under **Projects**, select the required project. 
2. Go to **Design Studio** > **Test Cases**. 
3. Select the required test case. 
4. Select the **Information** **Panel** (**i**) icon. The **Details** tab opens. 
5. Under **Tags**, enter the required tag name and press **Enter**. 
6. Select **Save**. 

{% hint style="info" %}
**Note**:

* Enter each tag separately and press **Enter** to add it. 
* Tagged test cases are displayed when you add test cases to an **Execution List**, making it easier to identify and select the required test cases. For complete filtering steps, see [Filter Tag](/avo-assure/create-and-execute-tests-with-design-studio/working-with-execution-section/features-in-execution-section-1/filter-tag.md).
* If the **Save** button is disabled, enter a description in the **Description** text box to enable it.
  {% endhint %}

![](https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FWUWJm9ryWDHj6ygT5M4z%2Funknown.png?alt=media\&token=e961ce9f-ef88-459a-8057-231594fef6a0)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.avoautomation.com/avo-assure/create-and-execute-tests-with-design-studio/working-with-test-case-section/features-in-test-case-section-1/tag-test-case.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.