Idera Xray Jira Cloud App Integration
Vera Configuration
Synchronization Policy
The Synchronization policy must be updated must be updated to reflect the following connection information.
{
"System": "JIRA",
"Name": "<Name of VERA Server>",
"Server": "https:<server name>.atlassian.net/",
"Service Account": "<emailtesting@domain.com>",
"Service Password": "<encrypted password>",
"Urls": {
"Browser": "https://<servername>.atlassian.net/browse/{Key}",
"API": "https://<server name>.atlassian.net/rest/api/2/issue/{Issue ID}"
},
"Linked Locations": [
{
"Name": "Xray Cloud",
"System": "Xray Cloud"
}
]
}
{
"System": "Xray Cloud",
"Name": "Xray Cloud",
"Server": "https://xray.cloud.getxray.app/api/v2",
"Service Account": "<service account>",
"Service Password": "<service account password>",
"Urls": {
"Browser": "https://xray.cloud.getxray.app/api/v2/",
"API": "https://xray.cloud.getxray.app/api/v2/"
}
}
Records Management Policy
The Records Management Policy must be updated to reflect the desired fields that will be displayed in VERA. Details specific to each of the entities below can also be added to allow VERA to display those as part of the record.
Xray entity | Required Field Definitions |
---|---|
Jira XRay Cucumber Test | Test Type, Summary, Scenario, Repository |
Jira XRay Generic Test | Test Type, Summary, Definition, Repository |
Jira XRay Manual Test | Test Type, Summary, Repository |
Jira XRay Test Run | Status, Executed By, Started On, Finished On, Duration, Comment, Assignee, Test Environments, Fix Versions |
Click on this link to download a sample file.
Xray App Configuration
Configure Xray App to enforce pre-execution and post execution approval controls on Xray Tests and Executions.