Skip to content
Plune Plune Plune Docs

The revisions of this case’s content, newest first

GET
/v1/test-cases/{id}/revisions
 
curl --request GET \
  --url https://beta-api.plune.ai/v1/test-cases/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/revisions \
  --header 'Authorization: Bearer <token>'

The title, description, precondition, parameters and body the case had at each of its versions (#1255) - kept whenever the version moves (the version moves exactly when that content does). A case from before the feature starts at the version it had then. At most the newest 100, without the content: changes says what a revert to each would change.

Authorizations

Section titled “Authorizations ”

Parameters

Section titled “ Parameters ”

Path Parameters

Section titled “Path Parameters ”
id
required
string format: uuid

Responses

Section titled “ Responses ”

200

Section titled “200 ”

The revisions

Media type application/json
object
revisions
required
Array<object>

The authored content of a case at one version (#1255): kept whenever the version moves, the newest 100 listed.

object
version
required
integer
>= 1
createdAt
required
string format: date-time
current
required

This is the content the case has now.

boolean
changes
required

What a revert to this revision would change: the fields that differ from the case now (body is the steps, the expected result, the spec or the prompt). Empty for the current one.

Array<string>
Allowed values: title description precondition examples body
Example 
{
  "revisions": [
    {
      "changes": [
        "title"
      ]
    }
  ]
}

401

Section titled “401 ”

No / invalid token or session

404

Section titled “404 ”

Not found or not yours

Media type application/json
object
error
required
string
Example generated
{
  "error": "example"
}