Skip to content

Conversation

@delatrie
Copy link
Contributor

Context

The PR introduces the globalLabels configuration property that takes an object whose values must be strings. The key-value pairs of the object are converted to Allure labels for all test results created during the run. This is an alternative to using environment variables, which is the subject of #597.

Example

{
  "allure": {
    "globalLabels": {
      "epic": "Core logic",
      "owner": "John Doe <email>",
      "layer": "unit"
    }
  }
}

Extra changes

  • fix schema link in allureConfig.json of SpecFlow testing projects

Checklist

Base automatically changed from env-labels to main October 16, 2025 09:58
@delatrie delatrie changed the title feat(nunit,xunit,reqnroll,specflow): introduce the globalLabels config property Introduce the globalLabels configuration property that affects all test results in the run Oct 16, 2025
@delatrie delatrie changed the title Introduce the globalLabels configuration property that affects all test results in the run Introduce the globalLabels configuration property that affects all test results in a run Oct 16, 2025
@delatrie delatrie merged commit 29c23c9 into main Oct 16, 2025
6 checks passed
@delatrie delatrie deleted the global-labels branch October 16, 2025 10:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants