> 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/organising-your-tests.md).

# Naming your tests

Learn how you can structure your tests to make it clean and useful! Learn effective test organization techniques to streamline your testing process with BugBug's comprehensive guide.

Think of a naming convention early, so that you can still find your way around when you have hundreds of tests.

A few ideas that work well:

* start with the area of the app, for example `Checkout - pay with card` or `Login / wrong password`
* use the same words for the same things in every test name
* use special characters such as slashes or emojis if they help you scan the list

[Searching](https://docs.bugbug.io/organizing-tests/searching-tests.md) looks for your text in test names and test notes. It is case insensitive, so it doesn't matter whether you use capital or small letters.

{% hint style="info" %}
Names are not the only way to keep tests in order. Group tests in [folders](https://docs.bugbug.io/organizing-tests/organizing-tests-with-folders.md) and label them with [tags](https://docs.bugbug.io/organizing-tests/tags.md), then filter the tests list by tags.
{% endhint %}

## Renaming a test

You can rename a test in two ways.

### On the tests list

Open the **...** menu in the test's row and choose **Rename**.

![](https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2Fe0iZMgpytgxx3O1F44Q8%2FScreenshot%202022-04-11%20at%2012.19.26.png?alt=media\&token=79410e5e-d9b6-4ff2-962b-107345dab8bf)

### On the test page

Open the test and click its title, or choose **Rename** from the test's actions menu.

![](https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2F6qMcRxpR1OhFHEPXtD5R%2FScreenshot%202022-04-11%20at%2012.18.37.png?alt=media\&token=a3fddcdf-71f3-40c0-a9f3-17c413c89657)


---

# 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/organising-your-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.
