DESTRUCTIVE

delete_test_case

Deletes a test case with its steps and versions after the person confirms; deprecating keeps it on the record instead.

Delete a test case by test_case_id, with its steps and its versions. Its reference is never reused. The removal goes through the same action the Test Cases page runs and test_case.deleted goes out. The tool is destructive: a Heimdall turn pauses for the person's confirmation and an MCP client asks before sending. Prefer moving a case to deprecated with update_test_case, so the record keeps the script and the results it gave. A staff token with test-case:delete on the project is needed.

Requires ability

The token behind the MCP session must hold it, or the call is refused with TOKEN_MISSING_ABILITY.

Annotations

Destructive

A client that honours annotations asks a person before running it.

Arguments

test_case_id*string

UUID of the test case to delete.

What it returns

{  "data": {    "test_case_id": "b7c8d9e0-f1a2-4b3c-8d4e-5f6a7b8c9d0e",    "deleted": true  }}

How it fails

RESOURCE_NOT_FOUND

unknown test_case_id, or a case outside the token's scope or the person's visibility.

FORBIDDEN

the token is a client guest's, or the holder's role on the project does not carry test-case:delete.

TOKEN_MISSING_ABILITY

token lacks test-case:delete.

How is this guide?

Last updated on