Allure adapter for Cucumber is not generating a proper story label in the results when @allure.label.story:Dummy_Story label is used
vvgorceac opened this issue · 2 comments
Describe the bug
Allure adapter for Cucumber is not generating a proper story label in the results when @allure.label.story:Dummy_Story label is used
To Reproduce
Having following test scenario (full example with the framework https://github.com/vvgorceac/framework-dummy-example):
@allure.id:1
@allure.label.story:Dummy_Story
Scenario: Photo endpoint should provide a list of photos
Given user sends a requests for list of photos
Then user receives a valid response
And user removes all photos that have 'albumId' different than 100
And user removes all photos that do not contain word 'error' in the title
results in the following in labels section of test result file:
"labels": [
{
"name": "tag",
"value": "allure.id:1"
},
{
"name": "tag",
"value": "allure.label.story:Dummy_Story"
},
{
"name": "host",
"value": "gogi.local"
},
{
"name": "thread",
"value": "91514@gogi.local.TestNG-PoolService-0(18)"
},
{
"name": "feature",
"value": "Dummy Example"
},
{
"name": "story",
"value": "Photo endpoint should provide a list of photos"
},
{
"name": "suite",
"value": "Dummy Example"
},
{
"name": "testClass",
"value": "Photo endpoint should provide a list of photos"
},
{
"name": "framework",
"value": "cucumber4jvm"
},
{
"name": "language",
"value": "java"
},
{
"name": "gherkin_uri",
"value": "classpath:features/Example.feature"
},
{
"name": "package",
"value": "features.Example_feature.Dummy Example"
}
],
Expected behavior
Scenario name is not used as story in test results
P.S. Support ticket link from Allure Test Ops https://help.qameta.io/support/tickets/386. Opening bug here as it was suggested by support team.
@vvgorceac
thanks for the relorting this. We'll review and plan the fix.
Labels from tags are now processed during report generation for both Allure TestOps and Allure Report