Page History

Versions Compared

...

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
Import existing Cucumber tests using the REST API (e.g., from an existing code base which may have tests, and their corresponding step implementation)
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.
Execute tests in the CI environment.
Report results to Xray, using the REST API or the Jenkins/Bamboo plugins.
Repeat from step 1 onwards.

Info

title	Please note

This flow will work fine as long as:

An unique tag "@id:xxx" is added to each Scenario/Scenario Outline within the file. The id just needs to be unique (e.g. sequential) within the feature file
The path of the feature file is not changed

Is any of the previous conditions is not satisfied then new and duplicated Tests, and Pre-Conditions, may be created.

...