Tags

Overview

Tags are organization-wide labels with per-project associations. Use them to categorize runs by environment (staging, production), feature area (auth, payments), test type (smoke, regression), or any custom dimension.

Because tags travel with every launch and test case, they become the fastest way to slice your quality data. A single tag lets you answer questions like "how stable is the payments area this sprint" or "what is the pass rate of smoke runs on staging" without building any custom reports. Tags are shared across the organization, so the same vocabulary works in every project and in cross-project analytics.

Creating Tags

• Navigate to the Tags page from the sidebar.
• Click "Add Tag" to create a new tag.
• Choose a descriptive name.
• Pick a color for visual identification.
• Tags are displayed as colored cards in a grid layout.

Using Tags

• Apply tags to test runs via reporter configuration.
• Apply tags to test cases in the case editor.
• Tags appear as colored badges throughout the UI.

You can pass tags from your test reporter configuration. For example, tag runs with the environment name or CI branch. Tags sent by a reporter are created automatically on first use, so your CI pipeline never fails because a label does not exist yet.

Tagging Strategies

A small, consistent tag vocabulary beats a large ad-hoc one. Most teams get the best results from three or four stable dimensions:

• Environment: staging, production, preview. Compare the same suite across environments to catch config-only failures.
• Test layer: smoke, regression, e2e, api. Filter trends by layer to see where instability actually lives.
• Feature area: auth, payments, reporting. Combine with releases to judge readiness of a specific area.
• Team or ownership: route failures to the right people when several teams share one project.

Agree on lowercase naming and singular form (smoke, not Smoke-Tests) before rolling tags out to CI. Renaming later is possible, but a consistent convention from day one keeps historical filters useful.

Filtering with Tags

• On the Launches page, filter runs by one or more tags.
• On the Test Cases page, filter cases by tags.
• On the Trends page, filter analytics by tags to compare environments or feature areas.
• Tags work alongside other filters (status, date range, etc.).

Tag Statistics

• Each tag card shows usage statistics.
• See how many runs and cases use each tag.
• Identify underused or heavily-used tags.

Managing Tags

• Edit tag name or color at any time.
• Delete tags that are no longer needed.
• Deleting a tag removes it from all associated runs and cases.