Update multiple 'TestRun' existing entities

PUT 
/testrun/bulk

Updates multiple existing 'TestRun' entities. Returns a full updated entity list including (optional) modification metadata.

Request

Query Parameters

force boolean

Forces the update even if '_etag' is missing or not matching.

application/json

Body

array

required

• Array [

id integer

The unique entity id - must be a positive integer

title string
A descriptive title for this entity or mapping (1 to 200 characters)
Example: A Descriptive Title
is_deleted boolean

If the entity has been soft-deleted this value is true

created_at date-time
The creation time for this entity or mapping value
Example: 1970-01-01T00:00:00.000Z
created_by number
The creator user id of this entity or mapping value - or zero if created by the system
Example: 0
modified_at date-time
The last modification time for this entity or mapping value
Example: 1970-01-01T00:00:00.000Z
modified_by number
The id of the user who last modified or undeleted this entity or mapping value - or zero if modified by the system
Example: 0
deleted_at date-time
The soft-deletion time for this entity or mapping value
Example: 1970-01-01T00:00:00.000Z
deleted_by number
The id of the user who deleted this entity or mapping value - or zero if deleted by the system
Example: 0
_etag stringrequired

A tag for detecting conflicting modifications - current value (may be empty) must be passed along in an update (or update must be forced)

project_id integer

The project id this entity or mapping belongs to

testplan_id integer
The optional id of the test plan this test run is associated with
Example: 0
closed_at date-time
The time this run was closed - all referenced test case data uses this as a historic timestamp
Example: 1970-01-01T00:00:00.000Z
closed_by number
The id of the user who closed this test run
Example: 0
is_closed boolean

Whether the test run is closed or not - closed runs can not be modified until reopened

description string
An optional description for this test run (can be a rich text document)
Example:

• ]

Responses

200

Returns an array of TestRun.

application/json

Schema

Schema

• Array [

id integer

The unique entity id - must be a positive integer

title string
A descriptive title for this entity or mapping (1 to 200 characters)
Example: A Descriptive Title
is_deleted boolean

If the entity has been soft-deleted this value is true

created_at date-time
The creation time for this entity or mapping value
Example: 1970-01-01T00:00:00.000Z
created_by number
The creator user id of this entity or mapping value - or zero if created by the system
Example: 0
modified_at date-time
The last modification time for this entity or mapping value
Example: 1970-01-01T00:00:00.000Z
modified_by number
The id of the user who last modified or undeleted this entity or mapping value - or zero if modified by the system
Example: 0
deleted_at date-time
The soft-deletion time for this entity or mapping value
Example: 1970-01-01T00:00:00.000Z
deleted_by number
The id of the user who deleted this entity or mapping value - or zero if deleted by the system
Example: 0
_etag stringrequired

A tag for detecting conflicting modifications - current value (may be empty) must be passed along in an update (or update must be forced)

project_id integer

The project id this entity or mapping belongs to

testplan_id integer
The optional id of the test plan this test run is associated with
Example: 0
closed_at date-time
The time this run was closed - all referenced test case data uses this as a historic timestamp
Example: 1970-01-01T00:00:00.000Z
closed_by number
The id of the user who closed this test run
Example: 0
is_closed boolean

Whether the test run is closed or not - closed runs can not be modified until reopened

description string
An optional description for this test run (can be a rich text document)
Example:

• ]

Example (from schema)

[
  {
    "id": 0,
    "title": "A Descriptive Title",
    "is_deleted": true,
    "created_at": "1970-01-01T00:00:00.000Z",
    "created_by": 0,
    "modified_at": "1970-01-01T00:00:00.000Z",
    "modified_by": 0,
    "deleted_at": "1970-01-01T00:00:00.000Z",
    "deleted_by": 0,
    "_etag": "string",
    "project_id": 0,
    "testplan_id": 0,
    "closed_at": "1970-01-01T00:00:00.000Z",
    "closed_by": 0,
    "is_closed": true,
    "description": ""
  }
]

4XX

The request failed because invalid request parameters or data were supplied or access was denied.

application/json

Schema

Schema

code string
The error code describing the general error category.
Example: API_INVALID_INPUT_DATA
status integer

The HTTP status code.

message stringrequired

The actual error message describing the error in more detail.

reqid string

The request id for following up on specific errors.

Example (from schema)

{
  "code": "API_INVALID_INPUT_DATA",
  "status": 0,
  "message": "string",
  "reqid": "string"
}

5XX

The request failed because an error occurred during processing of the request.

application/json

Schema

Schema

code string
The error code describing the general error category.
Example: API_INVALID_INPUT_DATA
status integer

The HTTP status code.

message stringrequired

The actual error message describing the error in more detail.

reqid string

The request id for following up on specific errors.

Example (from schema)

{
  "code": "API_INVALID_INPUT_DATA",
  "status": 0,
  "message": "string",
  "reqid": "string"
}

Loading...