> For the complete documentation index, see [llms.txt](https://docs.bugbug.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bugbug.io/organizing-tests/searching-tests.md).

# Searching tests

Learn how to efficiently search and organize your tests using BugBug's comprehensive documentation. Boost your testing productivity today!

## Search the tests list

The search box is at the top of the tests list, next to the **New test** button. Type a keyword and the list shows the matching tests.

The search:

* looks for your text in test names and test notes
* is case insensitive, so it doesn't matter whether you use capital or small letters
* searches all tests in the project, not only the open folder

When you start typing, the list switches to the **All tests** view. When you clear the search box, you go back to the view and folder you had open before.

Tip: if you have hundreds of tests, think about [how to name your tests](https://docs.bugbug.io/organizing-tests/organising-your-tests.md).

![](https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2F70E7QsZckKj5nhKYId7o%2FScreenshot%202022-04-11%20at%2012.27.34.png?alt=media\&token=6f220f46-a924-4290-a6ae-78c11f92b8bd)

## Filter the tests list

Use the filters next to the list title to narrow the list down:

* **Status** - the result of the last run, for example only failed tests
* **Success rate** - tests below a chosen success rate, for example below 80%
* **Tags** - tests with the selected [tags](https://docs.bugbug.io/organizing-tests/tags.md)

You can combine filters with each other and with the search. Click **Clear filters** to remove them all.

## Sort the tests list

Use the **Sort by** dropdown next to the list title to choose the order:

* **Date created** (default)
* **Name**
* **Last result date**
* **Success rate**
* **Screen** - available when your tests use more than one screen size

In the same dropdown, choose **Ascending** or **Descending**.

![](https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2FHajiHkjI8t4mdDo26EJi%2FScreenshot%202022-04-11%20at%2012.25.18.png?alt=media\&token=a227a256-d5ce-4b38-9159-42df3b51873b)


---

# 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.bugbug.io/organizing-tests/searching-tests.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.
