List Reviews For Run — GET /api/v1/test-management/suite-reviews/by-run/{test_run_id}
List Reviews For Run
All suite reviews for a single run (used by the run-detail page).
Endpoint: GET /api/v1/test-management/suite-reviews/by-run/{test_run_id}
Authentication: Send a signed-in user’s access token in Authorization: Bearer <access token>, or an API key in X-API-Key: <API key>.
Parameters
Section titled “Parameters”| Name | In | Required | Type | Default | Description |
|---|---|---|---|---|---|
test_run_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 | array of SuiteReviewResponse (application/json) |
422 | Validation Error | HTTPValidationError (application/json) |
Errors this endpoint returns, read from its source code:
404, with the message “Test run 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 Management
- Operation ID:
list_reviews_for_run_api_v1_test_management_suite_reviews_by_run__test_run_id__get - Source code:
backend/app/routers/test_management_suite_reviews.py, line 204 - Specification: OpenAPI JSON