Import Results using Rest API
Working Sample
Please look at Sample Projects for Automation sections for a more concrete end-to-end example.
1. Use API Key for Importing Results
Please Generate API Key if you don't have for your selected project.
2. Import test results
Import process is divided into 3 sections.
- Get Upload file URL : This API gets all required test automation details from the user and responds with a URL to upload the results.
- Upload your test result file to generated URL : This API is used to upload the automation results file and imports test results.
- Check Progress : This API is used to check the progress of automation result import.
2.1 Get Upload file URL
This API gets all required test automation details from the user and responds with a URL to upload the results.
URL : https://{{Jira base URL}}/rest/qmetry/automation/latest/importresult
Method : POST
REQUEST HEADER :
- Content-Type : application/json
- {generated-api-key}
- Basic ZnJlZDpmcmVk
Authorization
This Automation REST API is protected by the restrictions provided by JIRA. You need to log in Jira using the basic Auth header. Follow below steps to generate basic Auth and pass it to request header :
1. Build a string of the form username:password
2. Encode the string in Base64 format.
3. Pass an "Authorization" header with content "Basic " followed by the encoded string. For example, the string "fred:fred" encodes to "ZnJlZDpmcmVk" in base64, so you would make the request as follows.
Authorization: Basic ZnJlZDpmcmVk |
Notes
- zip file must contain files of same format given in the 'format' param.
- Request must contain json raw body payload, form-data is not supported.
Request Parameters
Parameter | Type | Required | Description | Default |
---|---|---|---|---|
format | string | Yes | Format of result file to be imported. Supported formats:
| NA |
testCycleToReuse | string | No | Issue Key of the test cycle to be reused | New Test Cycle will be created. |
environment | string | No | Name of the environment on which test cycle has to be executed | No Environment |
build | string | No | Name of the build for test case execution | Blank |
isZip | boolean | No (Yes for QAF) | Pass true for ZIP upload or pass false for single file upload | false |
attachFile | boolean | No | Pass true to upload attachments in execution. For more details, Refer automation help documents. This parameter is supported only for-
| false |
fields | JSON | No | Provide additional fields to be added on test case or test cycle level. Refer to following table for more. Note : If cycle is reused, fields of test cycle will be ignored. | Blank |
Supported Fields
Supported Fields | Type | Test Cycle | Test Case | Default |
---|---|---|---|---|
labels | array | Yes | Yes | null |
components | array | Yes | Yes | null |
status | string | Yes | Yes | TO DO |
priority | string | Yes | Yes | Medium |
fixVersionId | number | Yes | Yes | null |
sprintId | number | Yes | Yes | null |
summary | string | Yes | No | Automated Test Cycle |
Sample Request
{ "format":"cucumber", "testCycleToReuse":"TR-PRJ-1", "attachFile":true, "isZip":false, "environment":"Chrome", "build":"1.0.0 beta", "fields":{ "testCycle":{ "labels":[ "label1", "label2" ], "components":[ "component1" ], "priority":"High", "status":"To Do", "sprintId":10000, "fixVersionId":10000, "summary":"Test Cycle Summary" }, "testCase":{ "labels":[ "label1", "label2" ], "components":[ "component1" ], "priority":"High", "status":"To Do", "sprintId":10000, "fixVersionId":10000 } } }
Responses
Response | Description |
---|---|
STATUS 200 | Returned if results file is uploaded successfully. The import process might take a while and you would be notified (by email or checking the status of the created test run) once the process completed. Example { "url": "https://{{jira base url}}/rest/qmetry/automation/latest/importresult/submitFile?trackingId=3d19c19d-935c-4d08-b3de-74a38b5042a0", "message": "Generated Upload URL is valid for one time use and will expire in 5 minutes.", "trackingId": "3d19c19d-935c-4d08-b3de-74a38b5042a0" } |
| Returned if import fails If unsupported framework is sent in request { "status":400, "errorMessage":"Framework ‘xyz’ is not supported.", "timestamp":"02/Apr/2020 04:58" } If zip file is not sent in QAF framework request { "status":400, "errorMessage":"Zip file format is required for QAF framework.", "timestamp":"02/Apr/2020 05:00" } If one or more fields have invalid value { "status": 400, "errorMessage": "The supplied fields are invalid", "errors": [ "Provided Component Name(s) xyz not found ", "Provided Label Name(s) xyz not found" ], "timestamp": "03/Mar/2020 15:32" } |
2.2 Upload test result file
This API is used to upload the automation results file and imports test results.
URL : {{URL generated from step 1}}
Method : POST
Request Header
- Content-Type :
multipart/form-data
- {generated-api-key}
- Basic ZnJlZDpmcmVk
Request Body - Result file to be uploaded. Supported file extensions: .json, .xml and .zip (zip file must contain files of the format given in the 'format' param).
Note: File Attachment must be passed in form-data.
Responses
Response | Description |
---|---|
STATUS 200 | Returned if file is uploaded successfully. |
STATUS 400 | Returned if file upload happens after URL expiration time or if Content-type=multipart/form-data header is not passed Example URL Expiry
{ "status": 400, "errorMessage": "You cannot upload multiple files with same URL. Please create new upload request.", "timestamp": "03/Apr/2020 15:32" }
|
STATUS 204 | Returned if file format is not valid. No Content |
2.3 Check Progress
This API is used to check the progress of automation result import.
GET
application/json
apiKey : {generated-api-key}
Responses
Response | Description |
---|---|
SUCCESS | Returned if parameters are validated successfully. Example { "format": "CUCUMBER", "fileName": "1585908845000_5fcfde02-c044-4cee-baaa-48336384ee1b.json", "processStatus": "SUCCESS", "importStatus": "SUCCESS", "startTime": "03/Apr/2020 15:44", "endTime": "03/Apr/2020 15:44", "fileSize": null, "trackingId": "5fcfde02-c044-4cee-baaa-48336384ee1b", "files": null, "detailedMessage": "File is imported successfully.", "extraAttributes": { "attachFile": false }, "summary": { "testCycle": "9nw44F4lfp", "testCasesCreated": null, "testCaseVersionsCreated": null, "testCaseVersionsReused": 3, "testStepsCreated": 0, "testCycleIssueKey": "AP-TR-5" } } |
FAILED | Returned if any validation fails Example
{ "format": "CUCUMBER", "fileName": "1585909023000_dc038259-434f-4748-aaa6-a453a05d5ca1.json", "processStatus": "VALIDATION/PARSING/CREATING_ASSETS/SUCCESS", "importStatus": "SUCCESS/INPROCESS/FAILED", "startTime": "03/Apr/2020 15:47", "endTime": "03/Apr/2020 15:47", "fileSize": null, "trackingId": "dc038259-434f-4748-aaa6-a453a05d5ca1", "files": null, "detailedMessage": "The supplied file is either empty or invalid.", "extraAttributes": { "attachFile": false }, "summary": { "testCycle": null, "testCasesCreated": null, "testCaseVersionsCreated": null, "testCaseVersionsReused": null, "testStepsCreated": null, "testCycleIssueKey": null } }
|
3. View imported test results
Please refer to View Imported Test Results section to view imported test results.