> 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/filtering-test-artifacts.md).

# Filtering Test Artifacts

The filtering test artifacts feature helps you quickly find test artifacts in Avo Assure by filtering them based on Created By, Assigned To, Status, and Tags. The filtering feature is available in the Element Repository, Test Case, Execution, and Test Data Management sections. This reduces the time required to locate test artifacts and makes it easier to access artifacts created or assigned to specific users.

## Filtering Test Cases

{% hint style="info" %}
**Note**: Use the same steps for **Element Repository**, **Execution** and **Test Data Management**.
{% endhint %}

To filter test cases, perform the following actions:

1. On the **Home** page, from **Projects** list, select required project.
2. Select **Design Studio**>**Test Case**.
3. In the **Test Case** pane, select **Filter** icon.
4. From the **Filter list** dialog, select required filter. Following are the filters which you can add:
   * **Assigned to**: Filters Test case assigned to specific user.
   * **Created by**: Filters Test case created by specific user.
   * **Status**: Filters Test case by the specific status.
   * **Tag**: Filters Test case by the specific tag. 

{% hint style="info" %}
**Note**: The **Tag** filter is available only in **Test Case**.
{% endhint %}

<img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2Fem4CpvK9VgUaEccWe3rc%2Funknown.png?alt=media&amp;token=b35d2033-3c78-4391-86d8-f03ee91fe34c" alt="" height="255" width="605">

5. Select **Apply**.

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

* The **Clear all** option helps to remove all applied filter.
* The **Cancel** option closes the filter options without applying the selected filters.
  {% 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 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/filtering-test-artifacts.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.