get_generation_log

The latest generation's per-section transcript. This is the tool for diagnosing a failed generation before fixing the Gherkin and retrying — see the guide.

Request

GET /api/v1/ops/projects/{project}/features/{feature}/generation/log

Parameter	In	Type	Required	Description
project	path	string	yes	The project's public id.
feature	path	string	yes	Feature id or name.

cURL

curl -H "Authorization: Bearer $TESTVIBE_API_KEY" \
  "$TESTVIBE_SERVER/api/v1/ops/projects/$PROJECT/features/12/generation/log"

MCP

Tool get_generation_log — { "feature": "12" }.

Response

{
  "featureId": 12,
  "featureName": "Login Functionality",
  "requestId": "a1b2c3d4-…",
  "sections": [
    {
      "section": "login-functionality",
      "title": "Login Functionality",
      "state": "completed",
      "conclusion": "failure",
      "statusReason": "Tests did not pass verification",
      "log": [
        "Exploring the login page…",
        "Generated 3 test cases from the scenarios.",
        "Verification: 2/3 passed — selector '#login-button' not found on retry."
      ]
    }
  ]
}

Each log line is a trimmed transcript entry (≤ 600 characters) from the generation agent's work on that section.

Errors

HTTP	When
404 not_found	No such feature, or this feature has never been generated.