Page History
...
Having those to guide testing, we could then describe and implement the Cucumber test scenarios using our favourite IDE.
The related statement's code is managed outside of Jira and stored in Git, for example.
...
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
rm -f features.zip zip -r features.zip src/test/resources/calculator/ -i \*.feature curl -H "Content-Type: multipart/form-data" -u admin:admin -F "file=@features.zip" "http://jiraserver.example.com/rest/raven/1.0/import/feature?projectKey=CALC" |
...
| Info | ||
|---|---|---|
| ||
Each Scenario of each .feature will be created as a Test issue that contains unique identifiers, so that if you import once again then Xray can update the existent Test and don't create any duplicated tests.
|
You can then export the specification of the test to a Cucumber .feature file via the REST API, or the Export to Cucumber UI action from within the Test/Test Execution issue or even based on an existing saved filter. As source, you can identify Test, Test Set, Test Execution, Test Plan or "requirement" issues. A plugin for your CI tool of choice can be used to ease this task.
...