Creates a new test run in QAComplete.
Use the operation to add a new manual test run to the Run History in your QAComplete project, or to start an automated test run on a specific test host.
When you create a new automated test run using this operation, the operation creates a record about the run in the Run History and leaves the test in the Awaiting Run status. Information about the test will be provided to the test host, so that it can start the run in accordance with the provided data. The automated test run begins automatically – no additional actions are required from your side.
Basic authentication using a user’s login and password. See Authentication for details.
The authenticating user must belong to a security group that has the Add privilege for Test Library.
To create a test, send a POST request to the following URL:
ProjectId : integer, required
The ID of the project, to which you want to add a test run.
In the request body, pass the
RequestTestPost object that describes the test to create.
|For this operation, either the TestId parameter or the TestSetId one is required. These parameters are marked with the asterisk (*).|
TestId : integer, required
The ID of the test to create a run for.
TestSetId : integer, required
The ID of the test set to create a run for.
TestConfigId : integer
The ID of the configuration to run the test on.
ReleaseId : integer
The ID of the release which should be tested during the run.
RunByHostId : integer
The ID of the host which should run the test (for automated tests).
IsSequential : boolean
Defines whether the test should belong to a sequence.
A sample request:
POST http://yourserver.com/rest-api/service/api/v2/projects/98429/testruns HTTP/1.1
Authorization: Basic am9obkBleGFtcGxlLmNvbTpwQHNzd29yZA==
A sample request made by using cURL:
curl -u email@example.com:p@ssword -d @testrun.txt -H "Content-Type: application/json" -H "Accept: application/json" http://yourserver.com/rest-api/service/api/v2/projects/98429/testruns
If successful, the operation responds with HTTP status code 200. The response is a JSON object with information on the test run.
A sample response:
HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8
"run_by_user_name": "Smith, John ",
"status_code": "Awaiting Run",
The ID of the test run.
The ID of the release for which the test run is performed.
The ID of the project the test run belongs to.
The ID of the user who performed the test run.
The name of the user who performed the test run.
Shows if the test belongs to a sequence.
The status code of the test run.
Shows how the test is executed.
The date the test run started.
The date the test run finished.
The number of tests performed during the run.
Shows how many tests passed successfully during the run.
Shows how many tests failed during the run.
Shows how many tests were blocked during the run.
Shows how many tests were not performed during the run (for paused runs).
The overall test run time in seconds.
The overall test run time in the
The ID of the test run in the schedule.
The name of the test host used to perform the run (for automated tests).
If the operation fails, it returns the appropriate status code and (optionally) the error description in the response body.
If the project with the specified ProjectId does not exist or the authenticating user does not have rights to access the project, the operation returns the
Access is denied error.