Tags & Annotations

Tags and annotations are metadata that test frameworks attach to tests. They help you categorize, filter, and understand your test suite at a glance.

Tags

Tags are simple string labels attached to tests. Think of them as categories or groups. Common examples include smoke, regression, slow, or e2e.

Tags appear as clickable badges with a # prefix next to the test name. Clicking a tag filters the report to show only tests with that tag.

The Report Viewer includes a Tags tab that shows a summary table of all tags found in the report.

Filtering by Tag

You can filter tests by tag using FQL:

#smoke              # tests with the "smoke" tag
-#slow              # exclude tests tagged "slow"
#regression f:e2e   # regression-tagged tests in e2e files

Annotations

Annotations are richer metadata attached to individual test runs. Unlike tags, annotations have a type and an optional description, and they can reference a specific source code location.

Common annotation types include:

| Type | Meaning | |------|---------| | skip | Test is skipped | | fixme | Test is known-broken, to be fixed | | slow | Test is expected to take a long time | | fail | Test is expected to fail | | owner | Identifies the test owner |

Annotations appear as color-coded pills next to the test run:

• Red — fixme, fail
• Yellow — skip, slow
• Gray — owner
• Blue — any other type

If the annotation has a description, it appears in a tooltip on hover. When the description is a URL, it becomes a clickable link, which is useful for linking to tracking issues.

Use FQL to filter tests by annotation:

@skip               # tests annotated with "skip"
@fixme              # tests marked as fixme
-@slow              # exclude slow-annotated tests
@'needs review'     # annotation text containing spaces