Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
Xray DC V7.6.0
Description
Steps to reproduce it:
- Create a custom Test Type (Manage apps > Xray > Test Types).
- Create or change an existing Test issue, setting its Test Type to the custom Test Type that has been created.
- Using the endpoint POST /rest/raven/1.0/import/execution, send the following payload:
{
"tests": [
{
"testKey": "XB-5",
"status": "FAIL"
}
]
}
Expected result:
This request should have created a new Test Execution, with a Test Run for Test XB-5 with the status FAIL, like so:
{
"testExecIssue": {
"id": "10102",
"key": "XB-11",
"self": "http://localhost:8090/rest/api/2/issue/10102"
},
"testIssues": {
"success": [
{
"id": "10004",
"key": "XB-5",
"self": "http://localhost:8090/rest/api/2/issue/10004",
"testVersionId": 3
}
]
},
"infoMessages": []
}
Actual result:
We get a 200 response, but no Test Run is created, and we get the error message "
Invalid Test Type: None". See below:
{
"testExecIssue": {
"id": "10103",
"key": "XB-12",
"self": "http://localhost:8090/rest/api/2/issue/10103"
},
"testIssues": {
"error": [
{
"testKey": "",
"messages": [
"Invalid Test Type: None."
],
"testDefinition": ""
}
]
},
"infoMessages": []
}
This behavior started to happen on Xray version 7.6.0.
