> 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

### Use the search in table

The search box is located at the top of the table with your tests. Just type in the keyword and see the results. The search is case insensitive - that means that it doesn't matter if you use capital or small letters in the names of your tests.

Tip: if you have hundreds of test cases, think [how to name your tests.](/organizing-tests/organising-your-tests.md)&#x20;

![](/files/0X4YHG8t7CQSwXaPzEsQ)

### Sorting the tests list

If you want to see only failed tests, you can sort the table by status. Just click the table header once or twice to find the right sorting order.

![](/files/P846WgKr7RppsAAbCoB1)


---

# 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:

```
GET https://docs.bugbug.io/organizing-tests/searching-tests.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
