Upload blob data as an attachment to the given test case result in a given test run
POST/testrun/upload-attachment/:trId/:tcId
Upload blob data (in the request body) as an attachment to the given test case in a test run, with the blob metadata specified in the query parameters
Request
Path Parameters
The id of the Test Run
The id of the Test Case in the specified run the attachment will be added to
Query Parameters
The title for the attachment
The file name for the attachment (must be a valid cross-platform file name without path)
The mime type for the attachment - if not specified uses body content type
- application/octet-stream
Body
required
string
Responses
- 200
- 4XX
- 5XX
Returns 'Blob'
- application/json
- Schema
- Example (from schema)
Schema
The unique entity id - must be a positive integer
An optional descriptive title for the blob
If the entity has been soft-deleted this value is true
The project id this entity or mapping belongs to
The creation time for this entity or mapping value
1970-01-01T00:00:00.000Z
The creator user id of this entity or mapping value - or zero if created by the system
0
The last modification time for this entity or mapping value
1970-01-01T00:00:00.000Z
The id of the user who last modified or undeleted this entity or mapping value - or zero if modified by the system
0
The soft-deletion time for this entity or mapping value
1970-01-01T00:00:00.000Z
The id of the user who deleted this entity or mapping value - or zero if deleted by the system
0
A globally unique id for the blob
The MIME type of the blob (e.g. image/jpeg)
The file name of the blob when it was uploaded. Should have an extension compatible with the 'mime_type'
The size in bytes of the final blob
The category of the blob
An optional external key for identification
PROJ1_A123456
The base64 data of the blob when uploading - as an alternative to uploading the blob in a separate request (for small blobs)
BASE64 BLOB DATA
{
"id": 0,
"title": "string",
"is_deleted": true,
"project_id": 0,
"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,
"blob_id": "string",
"mime_type": "string",
"filename": "string",
"size": 0,
"category": "string",
"external_key": "PROJ1_A123456",
"data": "BASE64 BLOB DATA"
}
The request failed because invalid request parameters or data were supplied or access was denied.
- application/json
- Schema
- Example (from schema)
Schema
The error code describing the general error category.
API_INVALID_INPUT_DATA
The HTTP status code.
The actual error message describing the error in more detail.
The request id for following up on specific errors.
{
"code": "API_INVALID_INPUT_DATA",
"status": 0,
"message": "string",
"reqid": "string"
}
The request failed because an error occurred during processing of the request.
- application/json
- Schema
- Example (from schema)
Schema
The error code describing the general error category.
API_INVALID_INPUT_DATA
The HTTP status code.
The actual error message describing the error in more detail.
The request id for following up on specific errors.
{
"code": "API_INVALID_INPUT_DATA",
"status": 0,
"message": "string",
"reqid": "string"
}