Importing the execution results back to Jira.Executing the tests in the CI environment.Exporting Cucumber features from Jira to your Cucumber project.In a typical Cucumber Workflow, after having created a Cucumber project and the Cucumber tests specified in Jira, you may want to have a project that exports the features from Jira, executes the automated tests on a CI environment and then imports back its results.įor this scenario, the Jenkins project would be configured with a set of tasks responsible for: The Fix Version associated with the test execution (it supports only one value) Source code's revision being target by the Test Execution List of Test Environments separated by " " Key of the project where the Test Execution (if the T est Execution Key field wasn't provided) and the Tests (if they aren't created yet) are going to be created When this option is check, if you are importing multiple execution report files using a glob expression, the results will be imported to the same Test Execution Each ID is of the form " customfield_ID".Īnother option, which does not require Jira administration rights, is to invoke the "Get edit issue meta" in an existing issue (e.g., in a Test issue) as mentioned here. The custom field IDs can be obtained using the Jira REST API Browser tool included in Jira. As input, you can either specify issue keys (see the endpoint documentation for the server or cloud) or the ID of the saved filter in Jira. Some fields need to be configured in order to export the Cucumber Tests. It invokes Xray's Export Cucumber Tests REST API endpoint (see more information: server or cloud). The rules for exporting are defined here. This build step will export the Cucumber Tests (i.e., Scenario/Scenario Outlines) in. one build step which publishes the execution results back to Jira.one build step for importing Cucumber Tests from existing Cucumber features into Jira.one build step for exporting Cucumber Scenario/Scenario Outlines from Jira as.These need to be defined in the build configuration. Client Secret: obtained from Xray Cloud (more info here)īuild steps are the building blocks of the build process.Client ID: obtained from Xray Cloud (more info here).Configuration alias: a friendly name for the configuration.To add a new Jira Cloud connection, you need to specify some properties: The Jira Cloud configuration defines connections with Jira Cloud. The user present in this configuration must exist in the JIRA instance and have permission to Create Test and Test Execution Issues Jira Cloud
0 kommentar(er)
