New REST API endpoint for importing Cucumber feature files allowing new usage scenarios, including using Git as master
A new idempotent REST API endpoint will make it possible to import Cucumber Background, Scenario and Scenario Outlines from existing Cucumber .feature files. This endpoint will leverage new usage scenarios for Cucumber. Now you can either use Xray and Jira as the master for edition of Cucumber based Tests/Preconditions or you can use Git instead, for example, and keep using your favorite IDE for editing them. In this new supported workflow, Cucumber features will be "managed" in the source code VCS (versioning control system). This means that users will be editing features elsewhere, other than Jira, and will synchronize the scenarios contained within those features back to Jira. Therefore the master of information will be Git, SVN or whatever VCS is being used; you just need to make sure you follow some rules for tagging the Scenarios so they can be properly mapped to Xray. You can also migrate your existing Cucumber projects into Jira and start managing them in Xray instead.
Learn more about the new endpoint here and about the new supported Cucumber workflow and usage scenarios here. |