Skip to content
Plune 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
status
required

The verdict. passed/failed count an eval’s assertions, and a reporter’s result has none — read the verdict here. Stability skips skipped and blocked: neither ran the check.

string
Allowed values: passed failed broken blocked skipped
passed
required
integer
failed
required
integer
caseVersion

The version of the case this result was produced against (#1255) - GET /v1/test-cases/{id}/revisions/{version} shows the content it tested, whatever the case holds now.

integer
>= 1
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
files

The result’s finished files, oldest first, as on a run’s results list (#959) — present only when there is one. Read for the whole page at once, so a client shows a result’s screenshots without a request per row.

Array<object>

A file of a result, everything but its bytes (ADR 0040, ADR 0041). Only a finished file is ever shown: one that was announced with uploads and not yet completed is in no list.

object
id
required
string
name
required

The last segment of the name it was uploaded with, cleaned of credentials as a text is.

string
contentType
required

In the database (storage: db): image/png, image/jpeg, image/webp, application/json or text/plain — a log is text/plain. In the bucket (storage: bucket): the media type it was announced with, lower case and without parameters, any type.

string
size
required

Bytes as kept: in the database a picture at most 2 MiB and a text at most 512 KiB, counted after its credentials are cleaned, so it can differ from what was sent; in the bucket the size that was announced and found there.

integer
storage
required

db: Plune keeps the bytes, GET /v1/files/{id} returns them. bucket: they are in the project’s own bucket, and GET /v1/files/{id} answers 409 in_bucket (the way to read them is GET /v1/files/{id}/link).

string
Allowed values: db bucket
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 
{
  "results": [
    {
      "status": "passed",
      "files": [
        {
          "storage": "db"
        }
      ]
    }
  ],
  "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"
}