Page History
...
Code Block | ||||
---|---|---|---|---|
| ||||
image: "ruby:2.36" test: script: - apt-get update -qq - apt-get install unzip - gem install cucumber - gem install rspec-expectations - 'curl -u $jira_user:$jira_password "$jira_server_url/rest/raven/1.0/export/test?keys=$cucumber_keys" -o features/features.zip' - mkdir -p features - 'rm -f features/*.feature' - unzip -o features/features.zip -d features/ - cucumber -x -f json -o data.json - 'curl -H "Content-Type: application/json" -u $jira_user:$jira_password --data @data.json "$jira_server_url/rest/raven/1.0/import/execution/cucumber"' - echo "done" |
...
The GitLab configuration file .gitlab-ci.ym
l contains the definition of the build steps, including synchronizing the Scenarios/Backgrounds to Xray, extracting the cucumber specification from Xray, running the automated tests and submitting back the results.
.gitlab-ci.yml
|
|
In this example, we're using a variable filter_id defined in the CI/CD project level settings in GitLab. This variable contains the id of the Jira issues based filterhat based filter that will be used as source data for generating the Cucumber .feature files; it can be the key(s) of Test Plan(s), Test Execution(s), Test(s), requirement(s). For more info, please see: Exporting Cucumber Tests - REST.