curl -u <api-key>: https://cloud.bitbar.com/api/me/projects/PROJECT_ID/runs
curl -u <api-key>: https://cloud.bitbar.com/api/me/projects/PROJECT_ID/runs/ID
curl -X POST -u <api-key>: https://cloud.bitbar.com/api/me/projects/PROJECT_ID/runs/ID -d "displayName=DISPLAY_NAME"
curl -X DELETE -u <api-key>: https://cloud.bitbar.com/api/me/projects/PROJECT_ID/runs/ID
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
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
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/configcurl -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
}
...
}