Managing Test Runs
List test runs
curl -u <api-key>: https://cloud.bitbar.com/api/me/projects/PROJECT_ID/runs
Get a test run
curl -u <api-key>: https://cloud.bitbar.com/api/me/projects/PROJECT_ID/runs/ID
Update a test run
curl -X POST -u <api-key>: https://cloud.bitbar.com/api/me/projects/PROJECT_ID/runs/ID -d "displayName=DISPLAY_NAME"
Delete a test run
curl -X DELETE -u <api-key>: https://cloud.bitbar.com/api/me/projects/PROJECT_ID/runs/ID
Abort a test run
Note
Aborting a test run leads to test interruption and getting partial results.
curl -X POST -u <api-key>: https://cloud.bitbar.com/api/me/projects/PROJECT_ID/runs/ID/abort
Retry a test run
Note
Retrying a test run leads to test interruption (if tests are run), current results are removed, and the tests are started again. The device sessions get new IDs.
curl -X POST -u <api-key>: https://cloud.bitbar.com/api/me/projects/PROJECT_ID/runs/ID/retry
Get max available test run timeout
To learn the maximum available test timeout period for a test run, send the GET request to either endpoint:
curl -X GET https://cloud.bitbar.com/api/v2/users/{uerId}/runs/config
curl -X GET https://cloud.bitbar.com/api/v2/runs/config
This will return the maxTestTimeout
objects with the unit
and value
fields:
{ ... "maxTestTimeout": { "unit": "SECONDS", "value": 3600 } ... }