> For the complete documentation index, see [llms.txt](https://docs.qyrus.com/web-testing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qyrus.com/web-testing/analyze/tags.md).

# Tags

A tag is a label you put on a test script. Tags cut across modules and suites, so you can gather every script that matters to you — every login test, every smoke test — no matter where it is filed.

The **# Tags** mind map draws those groups as a picture.

## Tagging a script

Tags live on the script itself, so add them before you go looking for them.

1. Go to **Test Repository** and open the module that holds the script.
2. Click the **⋮** menu on the script's row and choose **Edit script**.
3. Type a tag in the **Tags** box and press Enter. Repeat for as many tags as you need.

   ![The Tags box on the Edit Script panel](/files/kY29ucbceocmDKlkeUrk)
4. Click **Update Script**.

You can also set tags when you first create a script — **New Script** opens a panel with the same **Tags** box.

## Viewing the tag map

On the project home page, under **Analyze** → **Mind maps**, click **# Tags**.

![The # Tags button on the project home page](/files/hGUJqnzoGNZsggpvahDU)

Each tag becomes a node, with the scripts carrying that tag hanging beneath it. A script tagged twice appears under both tags.

![Scripts grouped by tag](/files/4L38ancRNIAJrvxYyiI4)

If you see **No Tags Available**, no script in the project has a tag yet. Add one and come back.

## Narrowing the map

The panel on the right lists every tag in the project.

| Control         | What it does                   |
| --------------- | ------------------------------ |
| **Search Tags** | Filters the list as you type   |
| Tag checkboxes  | Show or hide that tag's branch |
| **Select all**  | Shows every tag at once        |

Use the zoom out and zoom in buttons at the top right when a project has more tags than fit on screen.

## What tags are good for

Tags are not only for the map. When you build a test suite you can tick **Auto add test scripts from tags**, and every script carrying the tags you name is pulled in — including scripts added later. That keeps a smoke suite current without anyone maintaining a list by hand.