diagnose_run
A failed run's full failure context in one call.
Request
GET /api/v1/ops/projects/{project}/runs/{runId}/diagnosisParameter
In
Type
Required
Description
curl -H "Authorization: Bearer $TESTVIBE_API_KEY" \
"$TESTVIBE_SERVER/api/v1/ops/projects/$PROJECT/runs/214/diagnosis"testvibe runs diagnose 214 # readable digest
testvibe runs diagnose 214 --json # includes the Gherkin and spec sourcesResponse
{
"runId": 214,
"status": "failed",
"verdict": "failed",
"featureId": 12,
"featureName": "Login Functionality",
"config": "Default",
"siteUrl": "https://demo.example",
"finishedUtc": "2026-06-11T09:15:42Z",
"summary": { "total": 3, "passed": 2, "failed": 1 },
"failures": [
{
"name": "Login > locked out user",
"status": "failed",
"durationMs": 12044,
"error": "TimeoutError: locator.click: Timeout 10000ms exceeded …"
}
],
"featureStatus": "generated",
"gherkin": "Feature: Login Functionality\n …",
"specs": [
{ "path": "Features/Default/Login Functionality.js", "content": "// executed spec source …" }
],
"log": "…last 4000 chars of the run log…",
"artifacts": [
{ "kind": "screenshot", "path": "…", "size": 48211, "url": "https://…(short-lived)" }
],
"hint": "Selector or timing failures in the spec usually mean the Gherkin needs tightening …"
}Field
Notes
Errors
HTTP
When
Last updated
Was this helpful?
