Editing & Deleting Tests

Update a test’s metadata, replace its plan steps or code safely, and delete tests one at a time or in bulk.

Editing a test

Metadata (name, description, priority) and, for backend tests, the dependency declarations (--produces, --needs, --category; see Creating Tests):

testsprite test update test_3a9f21c7 --name "Guest checkout v2" --priority p0

Frontend plan steps:

testsprite test plan put test_3a9f21c7 --steps ./updated-steps.json

The file is a JSON object with a planSteps array (≤ 200 steps, ≤ 256 KB). Optionally pass --expected-step-count <n>; the server returns 412 if the current count differs, so nothing is silently overwritten.

Backend test code:

# Safe: supply the codeVersion from your last create/update
testsprite test code put test_3a9f21c7 --code-file ./tests/create_order_v2.py --expected-version v3

# Overwrite regardless of version (audit-logged)
testsprite test code put test_3a9f21c7 --code-file ./tests/create_order_v2.py --force

codeVersion is an opaque token that changes on every code change. If the test has a newer version than --expected-version, the CLI exits 6; re-fetch the code and retry. The two flags are mutually exclusive. More in The Agent Loop.

Deleting tests

--confirm is required.

testsprite test delete test_3a9f21c7 --confirm
testsprite test delete-batch test_3a9f21c7 test_b1e04f2a --confirm
testsprite test delete-batch --all --project proj_8f0f6 --confirm
testsprite test delete-batch --all --project proj_8f0f6 --status failed --confirm

The CLI prints Deleted N, Skipped M, Failed K. A 404 counts as skipped, so already-deleted IDs are safe to pass. Exit 0 if everything was deleted or skipped, 1 if any deletion failed, 5 for validation errors.

Where to Go Next

Running Tests

Trigger runs and poll for verdicts

Reading Results

Failure bundles, steps, and run history