Labels and metadata
Allure labels are key-value pairs written into test result files by Allure adapters. Allure TestOps reads these labels on upload and uses them to populate test case attributes — custom fields, layers, members, issues, tags, and environment data.
The table below shows which attribute types Allure TestOps supports and what each one is used for.
| Attribute | Description | Used for |
|---|---|---|
| Custom fields | Epic, Feature, Story, Component, Microservice, and any other governed key-value pair | Test case filtering, test result filtering, analytics filtering, grouping (trees) |
| Test layer | Testing layer: UI, API, integration, etc. | Test case filtering, test result filtering, analytics filtering |
| Members | Author, owner, team lead, etc. | Test case filtering, test result filtering, analytics filtering, notifications |
| Issues | Linked bugs, features, or epics from an issue tracker | Test case filtering, test result filtering, analytics filtering, exporting data to issues |
| Tags | Lightweight free-form markers | Test case filtering, test result filtering, analytics filtering |
| Environment | Browser, host, OS, or other execution context | Test case history filtering, test result filtering, running tests on different environments |
Standard labels
The table below lists the standard labels used in Allure Framework. The Occurrence column indicates whether Allure takes only the first occurrence of the label (first) or all occurrences (all) when building the result file.
| Label | Occurrence | Allure Report v2 | Allure TestOps | Notes |
|---|---|---|---|---|
| ALLURE_ID | first | — | ✅ | |
| AS_ID | first | — | ✅ | Deprecated; use ALLURE_ID instead |
| ALLURE_MANUAL | first | — | ✅ | |
| package | first | ✅ | — | |
| testClass | first | ✅ | ✅ | |
| testMethod | first | ✅ | ✅ | |
| parentSuite | all | ✅ | ✅ | |
| suite | all | ✅ | ✅ | |
| subSuite | all | ✅ | ✅ | |
| epic | all | ✅ | ✅ | |
| feature | all | ✅ | ✅ | |
| story | all | ✅ | ✅ | |
| framework | first | ✅ | — | No default processing in Allure TestOps, but often used in user-defined mappings |
| language | first | ✅ | — | No default processing in Allure TestOps, but often used in user-defined mappings |
| layer | first | ✅ | ✅ | |
| thread | first | ✅ | ✅ | |
| host | first | ✅ | ✅ | |
| severity | first | ✅ | — | |
| tag | all | ✅ | ✅ | |
| owner | all | — | ✅ | |
| lead | all | — | ✅ | |
| custom labels | all | — | ✅ |
For language-specific examples of how to set labels in test code, see the Allure Report adapter documentation.
© Qameta Software Inc. All rights reserved.