I am trying to create test execution using API '/rest/raven/1.0/import/execution' with payload details provided in the documentation, test execution getting created. when I add fields like 'testCategoryId, fixVersion, versions, labels' I am getting the following error message "
Could you please provide your payload you are trying to create an issue?
It‘s just saying the fixVersion field is not matching format. What did you try to fill in this field?
Best
Stefan
Hi @Stefan Salzl adding my payload. I am trying to have values for following fields
I tried the input variations which I mentioned in my questions for the fields I mentioned above, but none creating successfully.
{
"info": {
"summary": "Execution of automated tests for release v1.0",
"description": "This execution is automatically created when importing execution results from an external source",
"user": "sm72",
"startDate": "2022-01-20T14:44:43Z",
"finishDate": "2022-01-20T14:44:43Z",
"projectKey": "AAAB",
"testEnvironments": [
"Windows"
],
"testcategoryId": "System Test",
"components": "EAT",
"versions": [{
"name": "v 1"
}],
"fixVersions": [{
"name": "v 1"
}],
"labels": ["mobile"]
},
"tests": [{
"testType": "System",
"start": "2022-01-20T13:19:41+00:00",
"finish": "2022-01-20T13:19:41+00:00",
"comment": "Comment on Test",
"status": "PASS",
"steps": [{
"status": "PASS",
"comment": "Coment on Test Step Result ",
"start": "2022-01-20T13:19:41+00:00",
"finish": "2022-01-20T13:19:41+00:00",
"actualResult": "Log file to step\n${File3}\nLog\n<a href=\"${filepath}\"><img src=\"${filepath}\"></a>, HTML\n",
"evidences": []
},
{
"status": "PASS",
"comment": "Coment on Test Step Result ",
"start": "2022-01-20T13:19:41+00:00",
"finish": "2022-01-20T13:19:41+00:00",
"actualResult": "Log\n<img src=\"${filepath}\"</img>, HTML\n",
"evidences": []
},
{
"status": "PASS",
"comment": "Coment on Test Step Result ",
"start": "2022-01-20T13:19:41+00:00",
"finish": "2022-01-20T13:19:41+00:00",
"actualResult": "Log\n<msg src=\"${filepath}\">img src=\"${filepath}\"</msg>, HTML\n",
"evidences": []
}
],
"testKey": "AAAB-2650"
}]
}
any input/suggestion is very much appreciated.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
not only for versions, I am getting the same kind of error message for component, test category and labels
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
According to this documentation of the Xray-JSON format there is a limitation of fields that can be set via Xray-API.
My personal assumption is that other fields would need to be set via Jira-API.
Best
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Stefan Salzl I created test execution separately and was able to able to update it separately using Jira API. Thanks, this helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
AWESOME!!!! great effort 🙌👌
Happy to know you got it working ;)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Singa Selva Sankar , can you pls provide URL and payload to only create test execution cycle using API. Am able to update an existing Test execution cycle using JSON result format through XRay API. But struggling to create a new test execution cycle using JIRA api.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.