Cucumber integration for the Serenity BDD Reporting library
Other
78
stars
74
forks
source link
Serenity Report: When feature level tags are used alone or in combination with scenario level tags to run the tests, serenity fails to generate tests report #113
When feature level tags are used alone or in combination with scenario level tags, serenity fails to generate tests report
Steps to Reproduce:
1) Write a Gherkin scenario outline and add a tag to the "Feature" keyword like in the below example.
2) Run the test from maven (mvn clean verify -Dcucumber.options="--tags @addaccount) and check the report.This would run all scenario present inside the feature tagged with @addaccount.
Expected:
All the scenarios in the Feature tagged with @addaccount should be run and Serenity should generate report containing the outcome of those scenarios.
Actual:
All the scenarios in the Feature tagged with @addaccount are run but Serenity fails to include the tests in the report.
Note: This happens when the scenarios are run with just the tag associated with the feature alone or alone with scenario level tags.
Environment:
1.8.41.8.01.6.7
**Scenario details:**
```
@addaccount
Feature: As a user, I should be able to add different types of accounts
@add
Scenario Outline: Add account
Given the account with following details: ,,
When I update the acccount to a
Then I should be informed of the successful account update
@bank_account
Examples: Add bank account
|accountType|heldBy |servicesSupported |
|bankaccount|individual|Deposit,Withdrawal |
@card_account
Examples: Add card account
|accountType|heldBy |servicesSupported |
|cardaccount|business |Deposit,Withdrawal |
|cardaccount|business |Deposit,Withdrawal |
```
**Project To Replicate:**
[sample.zip](https://github.com/serenity-bdd/serenity-cucumber/files/1562114/sample.zip)
Ram-Raghu
commented
6 years ago
Description:
When feature level tags are used alone or in combination with scenario level tags, serenity fails to generate tests report
Steps to Reproduce:
1) Write a Gherkin scenario outline and add a tag to the "Feature" keyword like in the below example. 2) Run the test from maven (mvn clean verify -Dcucumber.options="--tags @addaccount) and check the report.This would run all scenario present inside the feature tagged with @addaccount.
Expected:
All the scenarios in the Feature tagged with @addaccount should be run and Serenity should generate report containing the outcome of those scenarios.
Actual:
All the scenarios in the Feature tagged with @addaccount are run but Serenity fails to include the tests in the report.
Note: This happens when the scenarios are run with just the tag associated with the feature alone or alone with scenario level tags.
Environment: