For teams that keep test cases in Zephyr Scale, Xray or Azure Test Plans.

Your setup

Test cases in Zephyr Scale (Cloud, Server or Data Center), Xray, or Azure Test Plans.
A web app on a test environment that Certyn can reach, and a test account.
You want results back in the same tool, on a schedule or after each deploy.

Say this to Certyn

We connected Xray. Run the Checkout suite in project ABC against staging after each deploy, and write the results back.

Asks you to connect the tool on the Connections page first. You need:
- Zephyr Scale: an API token. The base URL only for Server or Data Center.
- Xray: a client ID and client secret from an Xray API key pair.
- Azure Test Plans: the organization URL and a personal access token with Test Plans read and write.
Finds the suite you name and shows you its cases, so you can check it.
Creates a process for that suite (app.process.create with type zephyr, xray or azure and the suite as source). It asks you first.
Sets the trigger (app.process.trigger.set): after each deploy, and/or a time with your time zone.
Each run pulls the current cases, runs them in a real browser, and writes each result back.

A run in your tool with a result per case: Passed, Failed, Blocked, or left untested for aborted or skipped cases.
A Certyn run report, and one Certyn issue per real product bug, with evidence.

The chat cannot connect these tools. Use the Connections page, then come back to the chat.
Xray cannot list Jira projects. Type the project key (for example ABC); the suites load after that.
Only the latest attempt per case is written back.
After each deploy fires when the environment gets a new version. Your pipeline sets it through the Environments API or a GitHub App deployment rule.