Get Enriched Test Case Detail Endpoint — GET /api/v1/runs/{run_id}/tests/{test_id}/rich-detail
Get Enriched Test Case Detail Endpoint
Versioned additive detail contract with optional recursive steps.
Endpoint: GET /api/v1/runs/{run_id}/tests/{test_id}/rich-detail
Authentication: Send a signed-in user’s access token in Authorization: Bearer <access token>, or an API key in X-API-Key: <API key>.
- You must have access to this test run.
Parameters
Section titled “Parameters”| Name | In | Required | Type | Default | Description |
|---|---|---|---|---|---|
run_id | path | yes | string (uuid) | ||
test_id | path | yes | string (uuid) | ||
X-API-Key | header | no | string or null | API key, as an alternative to the access token (see Authentication). |
Request body
Section titled “Request body”No request body.
Responses
Section titled “Responses”| Status | Meaning | Body |
|---|---|---|
200 | Successful Response | EnrichedTestCaseDetailResponse (application/json) |
422 | Validation Error | HTTPValidationError (application/json) |
Errors this endpoint returns, read from its source code:
404, with the message “Test case not found”
It can also return 401 if your credential is missing or expired, 403 if your credential does not allow this request, and 404 if the item does not exist or you cannot see it. Your role, your project membership and the key’s scope decide what a credential allows. See Errors and retries.
More details
Section titled “More details”- Group: Test Runs
- Operation ID:
get_enriched_test_case_detail_endpoint_api_v1_runs__run_id__tests__test_id__rich_detail_get - Source code:
backend/app/routers/runs.py, line 518 - Specification: OpenAPI JSON