Page History

...

• creation/edition of Scenario, Scenario Outline and Background entities
• validation with Cucumber (in different languages), Behave and SpecFlow
• centralized place to manage and do refactoring on Gherkin steps using the Automated Steps Library
• automatic provisioning of Gherkin based steps on the Automated Steps Library
• bulk import/update based on .feature files using the REST API and/or one of the available CI plugins
• export of .feature files containing Scenario, Scenario Outline and Background based on the respective Tests and Pre-Conditions through the UI, REST API and/or one of the available CI plugins

...

• """ (Doc Strings) - partial support (supported on creation/edition but not yet as reusable steps on the Automated Steps Library)
• | (Data Tables) - partial support (supported on creation/edition but not yet as reusable steps on the Automated Steps Library)
• @ (Tags), during the .feature export process based on the labels assigned to Test issues (e.g. Scenarios/Scenario Outlines) or during the import process
• # (Comments)

...

1. Specify Cucumber tests using natural language, in Jira.
2. Export Cucumber features from Jira to the CI environment, using the REST API.
3. Implement tests in code and commit them to the source code versioning system.
4. Execute tests in the CI environment.
5. Report results to Xray, using the REST API.
   
   

...

Pure VCS based workflow

...

In this workflow, the features are being "managed" in the source code VCS (versioning control system). This means that users will be editing features elsewhere, other than Jira, and they will want to synchronize the scenarios contained within those features to Jira. Therefore the master of information will be Git, SVN or whatever VCS is being used.

...

1. Create Cucumber tests (e.g. Scenario/Scenario Outlines) and their respective step code in some other tool.
   1. add an unique tag to each Scenario/Scenario outline, in the form of "@id:xxx", in which xxx is a number (e.g. 1, 2, 3, ...)
2. Import existing Cucumber tests using the REST API (e.g., from an existing code base which may have tests, and their corresponding step implementation) 
3. Export Cucumber features from Jira to the CI environment, using the REST API or the Jenkins/Bamboo plugins. It is crucial to use these exported features instead of the ones from the VCS, since the features exported from JIRA will contain additional tags that will allow several things, including the ability to correctly report the results to back to the correct entities in Jira, afterwards.
4. Execute tests in the CI environment.
5. Report results to Xray, using the REST API or the Jenkins/Bamboo plugins.
6. Repeat from step 1 onward.

...

Existing Cucumber tests are initially imported to Jira. Editing the tests can then proceed on the Jira side. While test editing can also occur simultaneously in Jira and in some other tool, it is highly recommended to keep it only on one side, preferably Jira. 

1. Create Cucumber tests (e.g., Scenario/Scenario Outlines) and their respective step code in some other tool.
2. Import existing Cucumber tests using the REST API (e.g., from an existing code base which may have tests, and their corresponding step implementation) 
3. Optionally, and in parallel, 
   1. Specify additional or edit existing Cucumber tests in natural language, in Jira.
   2. Implement remaining tests in code and commit them to the source code versioning system.
4. Export Cucumber features from Jira to the CI environment, using the REST API or the Jenkins/Bamboo plugins.
5. Execute tests in the CI environment.
6. Report results to Xray, using the REST API or the Jenkins/Bamboo plugins.
7. Repeat from step 3 onwards.

...