Skip to content

Cases as an XLSX — the tree, nodes or cases

GET
/v1/test-cases/export
curl --request GET \
--url https://beta-api.plune.ai/v1/test-cases/export \
--header 'Authorization: Bearer <token>'

The caller’s cases as one Excel workbook (#1235), in Testomat’s columns — ID, Title, Status, Folder, Priority, Description, Examples — which is what POST /v1/test-cases/import reads back, so the file imports to the same cases. ID is the case’s Testomat key when it came from Testomat, else empty; Title keeps its tags; Status is the type; Folder is /folder/suite (folder > a/b when a name has a slash); Description holds the texts in the Markdown of GET /v1/test-cases/markdown (## Preconditions, ## Steps, ## Expected result). Cases in no suite first, then each suite in tree order with its cases by position; the bin is not in it. With no parameter, every case; suiteId and caseId, each repeatable, keep the subtrees of those nodes and those cases — each case once. Automated and eval cases are written too; the import brings back manual ones.

suiteId
string format: uuid

A folder or suite — its subtree is in the file. Repeat for more than one.

caseId
string format: uuid

A case to put in the file. Repeat for more than one.

The workbook, one sheet Cases. X-Plune-Cases counts the cases in it; Content-Disposition names it cases.xlsx.

Media type application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
string format: binary
X-Plune-Cases
integer
Content-Disposition
string
Example
attachment; filename="cases.xlsx"

No / invalid token or session

A node or a case not in the caller’s project

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