Find 'TestCase' entities using the specified (query) parameters
GET/testcase
Same as POST /find, but serializing the query in the 'q' parameter instead of the request body
Request
Query Parameters
The DataReadParams query as JSON or base64-encoded JSON - See POST route
Responses
- 200
- 4XX
- 5XX
Returns FindResult of type 'TestCase' expanded with specified mapped values
- application/json
- Schema
- Example (from schema)
Schema
Array [
]
data
object[]
required
The unique entity id - must be a positive integer
A descriptive title for this entity or mapping (1 to 200 characters)
A Descriptive Title
An integer sort index for natural ordering of this entity or mapping value - value must be in range (-999999999999999,999999999999999)
If the entity has been soft-deleted this value is true
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 tag for detecting conflicting modifications - current value (may be empty) must be passed along in an update (or update must be forced)
The project id this entity or mapping belongs to
The global user id of the test case owner
The resolved display name of the owner user - read only
Reserved for future use
The template type used for the test case: STEPS or TEXT
A description of the precondition required for the test case (can be a rich text document)
The test case content - used with template STEPS (can be a rich text document)
The test case content - used with template TEXT (can be a rich text document)
The test case expected result - used with template TEXT (can be a rich text document)
The test case priority (This is a builtin-custom field)
1
The test case status (This is a builtin-custom field)
The test case type (This is a builtin-custom field)
The test case automation status (This is a builtin-custom field)
A test case time estimate (This is a builtin-custom field)
100
meta
object
required
{
"data": [
{
"id": 0,
"title": "A Descriptive Title",
"sort_index": 0,
"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,
"owner_user_id": 0,
"$owner_name": "string",
"type": "string",
"template": "string",
"precondition_text": "",
"content_text": "",
"steps_text": "",
"expected_result_text": "",
"priority": 1,
"status": "",
"testcase_type": "",
"automation": "",
"estimate": 100
}
],
"meta": {
"count": 0,
"limit": 0,
"offset": 0,
"totalCount": 0
}
}
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"
}