As a system, Xray should update how it generates Cucumber feature files to support multiple scenarios within a single Test

Description

Update Cucumber Scenario Export feature by:

• Implementing multiple Cucumber scenarios per Test
• Use the Test, folder title, or Test Set title as the “Feature”, depending on where the export is generated from.
• Use “Scenario” definition as the default title for a scenario, with a fallback on the Test title for a scenario.

User friction

• It is possible to include multiple “scenarios” in an Xray cucumber scenario field, but when the export occurs, we end up with scenarios embedded in scenarios. This is not proper cucumber BDD notation.
• It is not possible to create multiple “scenarios” for one feature ticket. They are crammed into one scenario field.
• When there is 1 scenario, the feature name and scenario are the same. 
• If a feature requires multiple scenarios, and those scenarios require examples (or datasets, as you call them). The cucumber export for multiple scenarios in the scenario field, one or more of which have examples, is practically unusable.

Steps to reproduce (right now):

1. Create a Test
2. Change Test Type to Cucumber
3. Define multiple Scenario in Scenario field
4. Generate Cucumber Feature files

Actual Result: 

IMPACT

What would improve if solved:

• Users can define multiple independent scenarios per Test issue
• Exported .feature files would be valid BDD syntax
• Align with standard BDD practices
• Reduced manual rework

Impact on stakeholders:

• Less manual effort to update
• Exported .feature files with valid BDD syntax
• Reduce risk of error

Current workaround:

• Manually edit exported .feature files
• Split Scenario into separate Test issues

CONTEXT & EXAMPLES:

Concrete example:

When exporting a Test with multiple Scenarios to a .feature file, the output is not proper Cucumber BDD notation.

Workaround risk:

• Risk of human error
• Increased manageability 

ADDITIONAL SUGGESTIONS:

• Stop using the “description” for BDD comments. 
• Allow for a custom “labels” field to be used for generating BDD tags