POST/projects/{ProjectId}/configurations

Applies to QAComplete 12.70 SaaS, last modified on January 11, 2021

Adds a new configuration to QAComplete.

Use the operation to register a new configuration in your project in QAComplete.

To replace the entire configuration (to redefine all the field values), use the …/configurations/{Id} (PUT) operation. To update individual fields, use the …/configurations/{Id} (PATCH) operation.

Authentication

Basic authentication using a user’s login and password. See Authentication for details.

Security Rights

The authenticating user must belong to a security group that has the Add privilege for Test Library.

Request Format

To create a configuration, send a POST request to the following URL:

http://{server}/rest-api/service/api/v2/projects/{ProjectId}/configurations
URL parameters

ProjectId  :  integer, required

The ID of the project to which you want to add a configuration.

Body parameters

In the request body, pass the RequestTestConfigurationPostV2 object that describes the configuration to create.

{
  "Id": "int",
  "FolderId": "int",
  "Title": "string",
  "Description": "string",
  "IsActive": "boolean",
  "CreateUserId": "int",
  "UpdateUserId": "int",
  "DateCreated": "Date",
  "DateUpdated": "Date",
  "OwnerUserId": "int",
  "OwnerName": "string",
  "NbrFilesNotSecured": "int",
  "FolderName": "string",
  "UserName": "string",
  "NbrFiles": "int",
  "NbrNotes": "int",
  "NotesDescription": "string",
  "OriginalId": "int",
  "ImportId": "int",
  "IsCBT": "boolean",
  "OperatingSystem": "string",
  "Browser": "string",
  "Resolution": "string",
  "CustomFields": [
    {
      "Id": "string",
      "Name": "string",
      "Value": "string"
    }
  ],
  "__permissions": {
    "Acl": "int"
  }
}

Some string property values (for example, OperatingSystem) are based on the choice lists defined in your QAComplete project. To view these values, go to the Test Library > Configurations > Tools > Manage Choice Lists screen in QAComplete.

Title  :  string (max 255 chars), required

The title of the test configuration.

FolderId  :  integer

The ID of the folder to which the test configuration belongs.

Description  :  string

The test configuration description. Can include an HTML markup.

IsActive  :  boolean

Defines whether the test configuration is active or not.

OwnerUserId  :  integer

The ID of the user who owns the test configuration.

OriginalId  :  integer

For importing: The original key of the imported item to retain.

ImportId  :  integer

The ID of the operation that imported the test configuration from an external file to the Test Library. 0, if the test configuration was not imported.

IsCBT  :  boolean

Shows whether the test configuration should support the CrossBrowserTesting.com capabilities.

OperatingSystem  :  string

For CrossBrowserTesting.com configurations: The operation system associated with the configuration.

Browser  :  string

For CrossBrowserTesting.com configurations: The browser associated with the configuration.

Resolution  :  string

For CrossBrowserTesting.com configurations: The resolution associated with the configuration.

CustomFields  :  array of objects

An array of CustomFields objects that describe custom fields and their values:


{
  "Id": "string",
  "Name": "string",
  "Value": "string"
}

Id  :  string, required

The unique identifier of the custom field. Must be in the CustomN format, where N is the custom field’s number (index).

Name  :  string

The field name.

Value  :  string

The field value.

A sample request:

POST http://yourserver.com/rest-api/service/api/v2/projects/11873/configurations HTTP/1.1
Host: yourserver.com
Connection: keep-alive
Content-Type: application/json
Accept: application/json
Authorization: Basic am9obkBleGFtcGxlLmNvbTpwQHNzd29yZA==
Content-Length: 38

{
  "Title": "Sample Configuration",
}

A sample request made by using cURL:

curl -u john@example.com:p@ssword -d {"Title": "Sample Configuration"} -H "Content-Type: application/json" -H "Accept: application/json" http://yourserver.com/rest-api/service/api/v2/projects/11873/configurations

Response Format

On success, the operation responds with HTTP status code 200. The response is a JSON object with information on the added configuration.

A sample response:

HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8
Content-Length: 466


{
        "id": 1,
        "folder_id": 0,
        "title": "Sample Configuration",
        "is_active": false,
        "create_user_id": 123456,
        "update_user_id": 123456,
        "date_created": "2016-08-31T09:13:59.9600000",
        "date_updated": "2016-08-31T09:13:59.9600000",
        "owner_user_id": 123456,
        "owner_name": "Smith, John ",
        "nbr_files_not_secured": 0,
        "user_name": "Smith, John ",
        "nbr_files": 0,
        "nbr_notes": 0,
        "original_id": 0,
        "import_id": 0,
        "project_id": 11873,
        "is_c_b_t": false,
        "custom_fields": [],
        "permissions": {
            "acl": 7
       }

Error responses

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.

If does not exist, the operation returns the File or directory not found error.

See Also

Configurations Resources

Highlight search results