update_feature
Update a feature's Gherkin and/or rename it. Body fields are optional — send what you want to change.
warning
Rejected with 409 conflict while the feature is generating. Updating the Gherkin does not regenerate tests — follow up with generate_feature.
Request
PATCH /api/v1/ops/projects/{project}/features/{feature}
| Parameter | In | Type | Required | Description |
|---|---|---|---|---|
project | path | string | yes | The project's public id. |
feature | path | string | yes | Feature id or name. |
gherkin | body | string | no | The new Gherkin source. |
name | body | string | no | The new feature name. |
group | body | string | no | Existing group name or public id; empty string ungroups. |
version_tags | body | string[] or null | no | REST: replace tags; null or an empty array clears them. Read responses use versionTags. |
- cURL
- CLI
- MCP
curl -X PATCH -H "Authorization: Bearer $TESTVIBE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"name": "Sign-in"}' \
"$TESTVIBE_SERVER/api/v1/ops/projects/$PROJECT/features/12"
testvibe features update 12 --file login.feature --name "Sign-in"
Tool update_feature — { "feature": "12", "name": "Sign-in" }.
Response
{ "ok": true }
Errors
| HTTP | When |
|---|---|
404 not_found | No such feature in this project. |
409 conflict | The feature is generating right now — wait or cancel first. |
Comment-, tag-, and whitespace-only Gherkin edits preserve generation state. Semantic changes can make the saved spec out of date; inspect specStale and regenerate when behavior changes. Group and version-tag edits are metadata changes. testvibe features update <feature> --group "" ungroups a feature.