Record Execution — PATCH /api/v1/test-management/plans/{plan_id}/items/{item_id}/execute
Record Execution
Endpoint: PATCH /api/v1/test-management/plans/{plan_id}/items/{item_id}/execute
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 plan.
Parameters
Section titled “Parameters”| Name | In | Required | Type | Default | Description |
|---|---|---|---|---|---|
plan_id | path | yes | string (uuid) | ||
item_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”| Content type | Body | Required |
|---|---|---|
application/json | ExecuteTestPlanItemRequest | yes |
Responses
Section titled “Responses”| Status | Meaning | Body |
|---|---|---|
200 | Successful Response | TestPlanItemResponse (application/json) |
422 | Validation Error | HTTPValidationError (application/json) |
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:
record_execution_api_v1_test_management_plans__plan_id__items__item_id__execute_patch - Source code:
backend/app/routers/test_management_plans.py, line 152 - Specification: OpenAPI JSON