Get List of all Automation Agents
...
Name | Located in | Required | Description | Default | Schema |
|---|---|---|---|---|---|
scope | header | yes | scope | - | string |
apikey | header | yes | Generated Automation API key | - | string |
headerRow | path | yes | Default value is 1 | - | string |
file | formData | yes | Your result file to be uploaded. Supported file extensions: .json, .xml and .zip (zip file must contain files of the format given in the 'entityType' param | - | string |
entityType | formData | yes | Format of result file to be imported. Supported formats:TESTNG or CUCUMBER or JUNIT or HPUFT or QAF | - | string |
cycleID | formData | no | Target Cycle Id or Cycle Name. Cycle Id can be fetched using List Cycle API and Cycle Name can be obtained from detail view of target Cycle. | - | string |
platformID | formData | no | Target Platform Id or Platform Name. Platform Id can be fetched using List Platform API and Platform Name can be obtained from detail view of target Platform. | - | string |
testsuiteId | formData | no | Target Test Suite ID or Entity Key. Testsuite id can be fetched using List Testsuite API and the Entity Key can be obtained from detail view of target Test Suite. This parameter will be ignored in case automationHierarchy for JUnit result upload is provided as 3 (multiple Test Suites). | - | string |
testsuiteName | formData | no | Provide test suite name for the new test suite If the auto-generated name is not desired. This parameter will be ignored in case automationHierarchy for JUnit result upload is provided as 3 (multiple Test Suites). | - | string |
projectID | formData | no | Target Project ID or project Key or project name. Project id can be fetched using List Poroject API and the Entity Key or name can be obtained from list view of target Project. | - | string |
releaseID | formData | no | Target Release ID or Release name. Release id can be fetched using List Release API from list detail of target Project. | - | string |
buildID | formData | no | Target Build ID or Build name. Build id can be fetched using List Build API from list detail of target Project. | - | string |
automationHierarchy | formData | no | The parameter has to be used only for TestNG and JUnit frameworks. Define the hierarchy of a Test case i.e. Test Case-Test Step or Test Case or Test Suite-Test Case. TestNG 1 Create Test Case -Test Step. The tag <class> is referred as Test Case and tag <test-method> as Test Step. (The default value is 1) JUnit 1 Create Test Case-Test Step. The tag <testsuite> referred as Test Case and tag <testcase> as Test Step. (The default value is 1) 3 Create Test Suite-Test Case. The tag <testsuite> referred as Test Suite and tag <testcase> referred as Test Case.In this case multiple Test Suites will be created. | - | string |
testcase_fields | formData | no | Mention system defined fields and user-defined fields for test case as shown in Test Case JSON format. All the mandatory fields other than Summary should be mentioned in this parameter. | - |
|
testsuite_fields | formData | no | Mention system defined fields and user-defined fields for test suite as shown in Test Suite JSON format. All the mandatory fields other than Summary should be mentioned in this parameter. This parameter will be ignored if existing Test suite Id is used to upload results. | - |
|
...
Status Code | Reason | Response Model |
|---|---|---|
200 | Test Suites created successfully | |
400 | Invalid json object or mandatory fields missing | - |
401 | Unauthorised or session expired | - |
500 | Returned when server connection times out | - |
...