Sign in
TestCaseManagement

Read the content of Zephyr test cases for use as a test-generation specification

Changed on

Returns what each case specifies -- objective, precondition, labels, and its steps or script -- for a model to read. The integration must belong to this workspace and be enabled, and each case's project must be one of its project_keys; a case outside them is out_of_scope without asking Zephyr. A step that calls another case is replaced by that case's steps, one level deep. Only a fixed set of fields is returned, because this content is intended for a model.

post/tcm/external/zephyr/workspaces/{workspace_id}/cases:content

Request

  • Base URL: https://api.mabl.com
  • URL: https://api.mabl.com/tcm/external/zephyr/workspaces/{workspace_id}/cases:content
  • Auth: one of:
    • HTTP basic
    • API key in header Authorization

Path parameters

workspace_idstring required

Request body

workspace_integration_idstring required

The integration to read the cases through. Case keys are unique only per Jira site, so the caller must say which one; it is validated against the workspace.

linksstring[] required

Case keys, e.g. PROJ-T12, at most 5 -- each costs upstream calls and prompt budget

Response

One entry per requested link, in request order

Example response

{
  "results": [
    {
      "link": "PROJ-T12"
    }
  ]
}

Changes