Skip to main content
GET
Get Test-run status and evidence

Authorizations

Authorization
string
header
default:dav_ak_live_your_token
required

Personal access token. The scopes granted at issuance determine both which operations the key may call and the ceiling on the resource permissions it can exercise. Each scope family is a ladder: projects:manage implies projects:write and projects:read; cards:manage implies cards:write and cards:read; and teams:manage implies teams:write and teams:read. These are named API capability bundles, not blanket domain roles: manage exposes only the permissions enumerated for that scope and never bypasses the acting user's current role-based access.

Path Parameters

projectId
string
required

Project id. May be compound in the form {projectId}--{branchName}.

Minimum string length: 1
testId
string
required

Id of the authored Test object in the source project.

Minimum string length: 1
runId
string<uuid>
required

Evaluation-run or Test-run id returned by its create operation.

Response

Current or terminal Test-run state.

runId
string<uuid>
required
projectId
string
required
branchName
string
required
testId
string
required
status
enum<string>
required

completed, failed, cancelled, and timed_out are terminal. failed means the Code execution or evaluation infrastructure failed; a valid low observation still completes and may resolve to a failing Test verdict.

Available options:
queued,
starting,
running,
evaluating,
cancelling,
completed,
failed,
cancelled,
timed_out
createdAt
string<date-time>
required
codeObjectId
string
evaluationRunId
string<uuid>
observation
number

Finite numeric observation committed to the Test's Results Value.

unit
string
verdict
object
evidence
object

Fixture-defined structured evidence. SYSTEM quality fixtures include transcript, final-tree, usage, and rubric summaries; callers must tolerate additional fixture-specific fields.

failure
object
startedAt
string<date-time>
completedAt
string<date-time>
updatedAt
string<date-time>