Test management · Native connection

Zephyr Scale and TestingOps: test cases, folders and test cycles

TestingOps reads the test cases of a Jira project from Zephyr Scale Cloud, sends AI-written and edited cases back with their steps into folders and records TestingOps runs as test cycles.

Native connection
Available with limits

Request a demo SmartBear: Zephyr Scale Cloud API access tokens

In short

Zephyr Scale and TestingOps in short

The Zephyr Scale connection uses a Zephyr Scale Cloud API access token. TestingOps reads the cases of a Jira project with name, objective, precondition, status and priority, and the steps of the first 200 cases of each read.

It creates cases in folders built from your folder path, updates the cases it is linked to by replacing their steps as a whole, and records a finished run as a test cycle with one execution per linked case.

Zephyr Scale Server / Data Center and Zephyr Squad are not supported, and cases cannot be deleted through the connection.

What it does

What it does for your testing

1
Cases come in with their steps
Input
The test cases of a Jira project
TestingOps
Reads up to 5,000 cases and the steps of the first 200, one request per case
Output
Imported cases; later cases arrive without steps and the preview marks them
2
Cases go out into folders
Input
Selected TestingOps cases
TestingOps
Creates missing test case folders from the folder path, then the cases with precondition and steps; linked cases get the new name and precondition and their steps replaced
Output
Zephyr Scale cases linked to TestingOps, with a copy of each changed case kept
3
A run becomes a test cycle
Input
A finished run
TestingOps
Creates a test cycle and an execution per linked case with Pass, Fail or Not Executed, the failure comment and the execution time
Output
A test cycle in the Jira project

Step by step

How it works

ConnectUnder Integrations → Project tools → Test management, open Zephyr Scale and paste an API access token from Zephyr Scale Cloud.
Read casesImport cases with Import from tool on Test Cases, or link the Jira project as a Test management source in Knowledge Base; pick the project by its key.
Send casesPush to TM creates new cases and updates linked ones; the import dialog can also update Zephyr Scale with cases you edited.
Report a runSend to TM on a finished run creates the test cycle.

Zephyr Scale returns steps through a separate call per case. For a larger project, a CSV export pasted under Import existing test cases in Knowledge Base is another way in: title, steps, expected result and priority columns are mapped automatically.

Connect

Setup

In Zephyr Scale Cloud, create an API access token.
In TestingOps, open Integrations → Project tools and, under Test management, select Zephyr Scale; paste the token as API access token, then select Test connection and Connect.
Import cases with Import from tool on Test Cases, push cases with Push to TM and report runs with Send to TM, picking the Jira project key as the target.

Documentation: SmartBear: Zephyr Scale Cloud API access tokens

Where you connect it in TestingOps: Integrations → Project tools → Test management → Zephyr Scale

Use cases

Run a Zephyr Scale regression set with AI

Trigger: A team imports the cases of its release regression project
Uses: Case names, objectives, preconditions and the steps of the first 200 cases
Agent activity: Imports them, can reformat them by instruction and marks duplicates
Result: Runnable cases in a TestingOps project
Condition: Cases after the first 200 of a read come without steps

Keep edited cases in step with Zephyr Scale

Trigger: A tester corrects steps in TestingOps after a UI change
Uses: The linked Zephyr Scale case
Agent activity: Write-back sends the new name, precondition and steps
Result: The Zephyr Scale case updated, its previous version kept in TestingOps
Condition: Steps are replaced as a whole, not merged

Report a release run as a test cycle

Trigger: The release regression run on RunningOps finishes
Uses: Results of the cases linked to the connection
Agent activity: Send to TM creates a cycle and one execution per case
Result: A test cycle with Pass, Fail or Not Executed per case
Condition: Uses the status names Pass, Fail and Not Executed

Capabilities

Capabilities and limits

What is read

Test cases of a Jira project: key, name, objective, precondition, status, priority
Steps of the first 200 cases of a read
Up to 5,000 cases per read

What is produced

Imported TestingOps cases or knowledge-base entries
Test cycles from TestingOps runs

Where it can write

New cases with precondition and steps in folders created from the folder path
Updates to linked cases: name, precondition and steps (replaced as a whole)
Test cycles with an execution per linked case: status, comment and execution time
Not written: deletions (the Zephyr Scale Cloud API has no case deletion) and defects

How it connects

A Zephyr Scale Cloud API access token, used against SmartBear's Zephyr Scale Cloud API

Account and permissions

TestingOps acts with the permissions of the token's owner

Limits

Zephyr Scale Cloud only: no Server / Data Center and no Zephyr Squad
Steps only for the first 200 cases of each read
An import does not rebuild the folder tree
Duplicates can be left out of an import but not deleted in Zephyr Scale
No live two-way sync; runs are reported when someone sends them

Example

Example: how a team uses it

Illustrative scenario, not a customer story.

A team keeps 140 cases for its insurance quote flow in Zephyr Scale Cloud and imports them into a TestingOps project. All 140 arrive with their steps, because the project is under the 200-case step limit.

After a redesign, a tester edits two cases in TestingOps and updates them in Zephyr Scale, which replaces their steps after TestingOps keeps copies. The release run on RunningOps is then reported as a test cycle with Pass or Fail per case.

Frequently asked questions

Does it support Zephyr Scale Server / Data Center or Zephyr Squad?

No. The connection talks to the Zephyr Scale Cloud API only.

Why do some imported cases have no steps?

Zephyr Scale returns steps through a separate call per case, so TestingOps reads steps for the first 200 cases of each read. Later cases come with name, objective and precondition only, and the preview marks them as without steps.

What happens to steps when a case is updated?

They are replaced as a whole with the TestingOps steps. Before that, TestingOps keeps a copy of the Zephyr Scale case, which you can restore.

Can duplicates be deleted in Zephyr Scale?

No. The preview can mark duplicates so they are left out of the import, but the Zephyr Scale Cloud API has no endpoint for deleting cases.

Which execution statuses are used?

Pass, Fail and Not Executed, with the failure message as the comment and the execution time of each case.

Next step

Bring a Zephyr Scale project to a demo and see its cases run and reported as a test cycle.

Request a demo More test management integrations