allure-framework / allure-cucumberjs

Deprecated, use https://github.com/allure-framework/allure-js instead
Other
15 stars 12 forks source link

Test scenarios are groupped by "Without feature" name not a correct one #2

Closed sgorbatenko closed 8 years ago

sgorbatenko commented 8 years ago

I have feature file like: @account Feature: Account management

Scenario: Add account Given I am on the Accounts page1 When I add new account1 Then I should see account details1

Scenario: Edit account Given I am on the Accounts page1 When I edit new account1 Then I should see account details1

Generated after I run protractor test and generate report I've got allure-results.zip img-2016-05-17-14-16-06

Why it is named as " Without feature" and not as "Account management" img-2016-05-17-14-21-17

igniteram commented 8 years ago

@sgorbatenko you have set the @account tag before the feature that is why it is not identifying, try this :

Feature: Account management @AddAccount Scenario: Add account Given I am on the Accounts page1 When I add new account1 Then I should see account details1

@EditAccount Scenario: Edit account Given I am on the Accounts page1 When I edit new account1 Then I should see account details1

It's always a good practice by giving tags at scenario level rather than feature level.

piociek commented 8 years ago

@sgorbatenko Thanks! I'll check what's wrong.

igniteram commented 8 years ago

@sgorbatenko @piociek up voting the above issue as i am also able to reproduce this issue, have to look at the root cause. Note this issue happens in "Behaviour" section

piociek commented 8 years ago

Works as intended. Please check this example: https://github.com/allure-framework/cucumberjs-allure-reporter/blob/master/features/label.feature

Closing.