testland/zephyr-scale-case-management

Author and manage Zephyr Scale Cloud test cases via the REST API v2 - create tests, attach steps, link to Jira issues, organise into folders, manage test cycles. Covers Bearer-token auth, the /testcases endpoints, the testScript / steps shape, and folder hierarchy. Use for pre-execution case authoring in Jira-anchored teams using Zephyr Scale (formerly TM4J). Distinct from Zephyr's test-cycle / execution endpoints which post results.

Quality

99%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Zephyr Scale Cloud API v2 reference

Name: testland/zephyr-scale-case-management
Rating: 79.2 (1 reviews)
Author: testland

Migration field map, folder + Jira-link operations, and response shapes for the Zephyr Scale Cloud REST API v2. Per smartbear.com/test-management/zephyr-scale (Cloudflare-protected; cite by stable URL). BASE, HEADERS, and resolve_jira_issue_id are defined in SKILL.md.

Migration target field map

Source field	Zephyr field
Title	`name`
Objective	`objective`
Preconditions	`precondition`
Steps	testScript items
Owner	`ownerId` (Jira user ID)
Priority	`priorityName` (project enum)
Status	`statusName`
Labels	`labels[]`
Component	`componentId` (Jira component)
Requirement traceability	`/links/issues`

Folders

def create_folder(project_key, name, folder_type="TEST_CASE", parent_id=None):
    r = requests.post(f"{BASE}/folders", json={
        "projectKey": project_key, "name": name,
        "folderType": folder_type,  # TEST_CASE / TEST_PLAN / TEST_CYCLE
        "parentId": parent_id,
    }, headers=HEADERS)
    r.raise_for_status()
    return r.json()

Folders nest; create the hierarchy first, then place cases.

Linking to Jira issues

def link_to_jira(test_case_key, issue_key):
    r = requests.post(f"{BASE}/testcases/{test_case_key}/links/issues",
                      json={"issueId": resolve_jira_issue_id(issue_key)},
                      headers=HEADERS)
    r.raise_for_status()

Requires the Jira REST API to resolve issue key -> issue ID separately. Trace back from cases to requirements via the linked-issues endpoint.

Response shapes

Create returns {"id", "key", "self"}; key is the project-prefixed id (PROJ-T123).
List returns {"values": [...], "startAt", "maxResults", "total", "isLast"}; page until isLast is true.

.tessl-plugin

references

zephyr-scale-api-reference.md

SKILL.md

tile.json