Sign in
TestCaseManagement

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

Changed on

Returns what each case actually specifies -- preconditions, steps, expected results -- normalised so the caller sees one structure whatever template the case uses. Unlike the lookup, which searches every enabled integration in the workspace, this names one: the integration must belong to this workspace and be enabled, and each case must lie inside its configured project and suite. Only fields on a fixed readable set are returned, because an instance may define text fields holding anything and this content is intended for a model. A case whose content lies entirely outside that set is reported no_readable_content rather than returned empty.

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

Request

  • Base URL: https://api.mabl.com
  • URL: https://api.mabl.com/tcm/external/testrail/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 whose instance holds these cases. Case ids are unique only per instance, so the caller must say which one; it is validated against the workspace.

linksstring[] required

Case links, at most 5 -- each costs an upstream call and prompt budget

Response

One entry per requested link, in request order

Example response

{
  "results": [
    {
      "link": "C71"
    }
  ]
}

Changes