Skip to content
Plune Plune Docs

This case’s past evaluations, newest run first

GET
/v1/test-cases/{id}/results
 
curl --request GET \
  --url https://beta-api.plune.ai/v1/test-cases/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/results \
  --header 'Authorization: Bearer <token>'

Two ways a Result reaches here. A CLI run attaches one when it carries an eval whose id matches the case’s evalId (ADR 0010); approving a Cairn proposal attaches the verdict the proposing run already measured, so a case born that way has history from the start.

Authorizations

Section titled “Authorizations ”

Parameters

Section titled “ Parameters ”

Path Parameters

Section titled “Path Parameters ”
id
required
string format: uuid

Responses

Section titled “ Responses ”

200

Section titled “200 ”

The case’s history

Media type application/json
object
results
required
Array<object>

One past evaluation of a case, derived from the Result stored at ingest.

object
id
required

The Result — pass it to POST /v1/review-items.

string format: uuid
runId
required
string format: uuid
createdAt
required
string format: date-time
passed
required
integer
failed
required
integer
verdictsPassed

Judge questions answered true across this result (BINEVAL). Both verdict counts are absent when nothing judged question-by-question — distinct from “judged, all passed”.

integer
verdictsFailed
integer
stability
required

How stable the case has been, measured as transitions INTO failure ÷ runs — not a failure rate. The two are different diseases: an eval that fails every time is broken (0 transitions, stable), one that alternates is a coin toss. Read runs/failures alongside level, or a permanently broken case looks fine.

object
score
required

Transitions into failure ÷ runs. 0 for a history of ≤ 1.

number
level
required
string
Allowed values: stable flaky critical
runs
required

Runs the score is based on — a score over 2 runs means little.

integer
failures
required
integer
Example 
{
  "stability": {
    "level": "stable"
  }
}

401

Section titled “401 ”

No / invalid token or session

404

Section titled “404 ”

Not found or not yours

Media type application/json
object
error
required
string
Example generated
{
  "error": "example"
}