Find 'TestCaseFolder' entities using the specified (body) parameters
POST/testcase-folder/find
Search for entities with the filters and arguments specified in 'DataReadParams' (see request schema), with optional mapping expansions via 'map'. Note that 'filter' should include a 'project_id' parameter if API key permissions are restricted to a single project.
Request
- application/json
Body
required
- Array [
- MOD1
- MOD2
- ]
- ByKeys
- MOD2
- MOD2
- Array [
- ]
- MOD2
- Array [
- ]
- Array [
- MOD2
- Array [
- ]
- MOD2
- Array [
- ]
- ]
- ByKeys
- MOD2
- MOD2
- Array [
- ]
- MOD2
- Array [
- ]
- Array [
- MOD2
- Array [
- ]
- MOD2
- Array [
- ]
- ]
- MapJoin
- MOD2
- MOD1
- MOD2
- Array [
- ]
- MOD2
- Array [
- ]
- ByKeys
- MOD2
- MOD2
- Array [
- ]
- MOD2
- Array [
- ]
- Array [
- MOD2
- Array [
- ]
- MOD2
- Array [
- ]
- ]
- ByKeys
- MOD2
- MOD2
- Array [
- ]
- MOD2
- Array [
- ]
- Array [
- MOD2
- Array [
- ]
- MOD2
- Array [
- ]
- ]
- ByKeys
- MOD2
- MOD2
- Array [
- ]
- MOD2
- Array [
- ]
- Array [
- MOD2
- Array [
- ]
- MOD2
- Array [
- ]
- ]
- ByKeys
- MOD2
- MOD2
- Array [
- ]
- MOD2
- Array [
- ]
- Array [
- MOD2
- Array [
- ]
- MOD2
- Array [
- ]
- ]
- MOD2
- Array [
- ]
- Array [
- MOD1
- MOD2
- Array [
- ]
- MOD2
- Array [
- ]
- ByKeys
- MOD2
- MOD2
- Array [
- ]
- MOD2
- Array [
- ]
- Array [
- MOD2
- Array [
- ]
- MOD2
- Array [
- ]
- ]
- ByKeys
- MOD2
- MOD2
- Array [
- ]
- MOD2
- Array [
- ]
- Array [
- MOD2
- Array [
- ]
- MOD2
- Array [
- ]
- ]
- ByKeys
- MOD2
- MOD2
- Array [
- ]
- MOD2
- Array [
- ]
- Array [
- MOD2
- Array [
- ]
- MOD2
- Array [
- ]
- ]
- ByKeys
- MOD2
- MOD2
- Array [
- ]
- MOD2
- Array [
- ]
- Array [
- MOD2
- Array [
- ]
- MOD2
- Array [
- ]
- ]
- MOD2
- Array [
- ]
- ]
pagination object
Pagination settings control how much data from a result is fetched
The offset the result starts at
Selects the page with the given id in the result, given a limit (= page size)
Adds a number of items before the start offset and after the limit (for pagination use)
The maximum number of result rows
order object[]
Controls the ordering of the result
Ordering by a pre-defined value sequence - the partial ordering of the given values in the result is preserved
The name of the column to order by
The name of the column to order by
Possible values: [asc
, desc
]
Either 'asc'ending or 'desc'ending order for the given column
Includes the total result count if pagination options were given
filter object
Filter/search terms
and object
and object
or object
and object
or object
or object
and object
or object
and object
or object
List of computed columns to include (by default includes all)
Only return the entity with the given id, returns one or none
Only return the entities with the given ids
map object
Map expression to expand properties or relationships with other entities
entities object
The list of entity names which are part of the mapping (for mapping relationship tables)
string
string
The entity name (for direct mapping via a foreign key)
ids object
A list of id tuples to filter by
Default value: false
Inverts the result to retrieve non-mapped entities
filter object
Filter/search terms
and object
and object
or object
and object
or object
or object
and object
or object
and object
or object
resultFilter object
Filter/search terms
and object
and object
or object
and object
or object
or object
and object
or object
and object
or object
Default value: false
Only returns a count instead of a list of entities
Default value: false
Only retrieves entity ids, omitting all other columns
Default value: false
Indicates that the mapping is optional and may be 'null' in the result
Default value: false
Includes deleted member entities in the mapping search result
Default value: false
Omits 'large' column/prop values (if available)
Omit the mapping result from result entities - For intermediate nested mappings
The entity to use as the result instead of the mapping relationship entity data
Default value: false
Also includes mapping even if result entity is specified
map object
Nested mapping starting from one of the member entities of this mapping
The Testiny platform API.
entities object
The list of entity names which are part of the mapping (for mapping relationship tables)
string
string
The entity name (for direct mapping via a foreign key)
ids object
A list of id tuples to filter by
Default value: false
Inverts the result to retrieve non-mapped entities
filter object
Filter/search terms
and object
and object
or object
and object
or object
or object
and object
or object
and object
or object
resultFilter object
Filter/search terms
and object
and object
or object
and object
or object
or object
and object
or object
and object
or object
Default value: false
Only returns a count instead of a list of entities
Default value: false
Only retrieves entity ids, omitting all other columns
Default value: false
Indicates that the mapping is optional and may be 'null' in the result
Default value: false
Includes deleted member entities in the mapping search result
Default value: false
Omits 'large' column/prop values (if available)
Omit the mapping result from result entities - For intermediate nested mappings
The entity to use as the result instead of the mapping relationship entity data
Default value: false
Also includes mapping even if result entity is specified
map object
Nested mapping starting from one of the member entities of this mapping
The Testiny platform API.
Includes soft-deleted entities in the result (if applicable)
Default value: true
Omits 'large' column/prop values (if available)
Default value: false
Omits entities which are not allowed to be read rather than return an error
Perform a history query given the asOf timestamp (if available)
Only returns ids in the result, omitting all other properties
Returns only the length of the result list instead of the result list itself
Responses
- 200
- 4XX
- 5XX
Returns FindResult of type 'TestCaseFolder' 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)
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
The creator user id of this entity or mapping value - or zero if created by the system
The last modification time for this entity or mapping value
The id of the user who last modified or undeleted this entity or mapping value - or zero if modified by the system
The soft-deletion time for this entity or mapping value
The id of the user who deleted this entity or mapping value - or zero if deleted by the system
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 id of the folder's parent in the tree structure (no cycles allowed)
An optional description for this test case folder (can be a rich text document)
meta objectrequired
{
"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,
"testcase_folder_parent_id": 0,
"description": "string"
}
],
"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.
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.
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"
}