Description
Right now, when importing a Cucumber .feature file, Features are automatically mapped as Requirements and Backgrounds as Pre-Conditions, and then the Scenarios/Scenario Outlines will generate Tests that will be created for them.
However, in cases where there are multi-level scenarios within the file (i.e., nested scenarios), sometimes it is desirable to create a Test only for the outermost scenario, and putting the inner scenarios in its description, as opposed to creating a Test for each of the scenarios (in this case, the outermost scenario will be empty).
Take the following .feature file as an example:
In this case, it could be desirable to create only 1 Test, for the outermost scenario, and have it be imported like this:
So this Suggestion would entail the creation of another tag (example: @ignore), that could be inserted above scenarios for them to be ignored. The scenarios associated with said tags should be treated as text and inserted in their parent scenario as description. If this tag is used on the outermost scenario of the .feature file, it should result in a failure (or be ignored).
Example:
Scenario: --> this scenario will create a Test
@ignore
Scenario: blah blah blah. --> this one will NOT, instead it will be used as description for the Test created by the parent scenario
Given ....
When ....
Then ....
And ....
Scenario: blah blah blah --> this scenario will create another Test
Given ....
When ....
Then ....
And ....
