Skip to main content
GET
Get a latest test execution

Authorizations

Authorization
string
header
required

Personal or account token.

Path Parameters

sub_test_unique_id
string
required

Sub-test identifier (sub_test_unique_id).

env_id
string
required

Environment identifier that scopes the request.

Response

Successful Response

duration_seconds
number
required

How long the execution took.

failure_count
integer
required

Number of failed rows or detected issues.

id
string
required

Identifier of this execution.

start_time
string<date-time>
required

When the execution started.

status
string
required

Extensible enum. Result of the execution. New values may be added over time.

Examples:

"PASS"

"WARN"

"FAIL"

"ERROR"

"SKIPPED"

"NO_DATA"

sub_test_unique_id
string
required

Stable identifier of the sub-test (a test can explode into several sub-tests, e.g. one per column). Use it to key latest executions.

sub_type
string
required

Sub-test type within the test (e.g. the anomaly type checked).

test_id
string
required

ID of the test that produced this execution.

column_name
string | null

Column this execution checked, when applicable.

description
string | null

Description of the test at execution time.

exception
string | null

Error message when the execution errored.

quality_dimension
string | null

Extensible enum. Data-quality dimension the test covers, when classified.

Example:

"completeness"

result_reason
string | null

Extensible enum. Why the execution produced its status, when Elementary could determine it.

Example:

"PERMISSIONS_ERROR"

synced_at
string<date-time> | null

When Elementary last synced this execution.