--- title: "TestRail, Xray and Zephyr Scale integration for design controls | Qualio" canonical: "https://www.qualio.com/integrations/test-tools" updatedDate: "2026-11-02T11:44:50.000Z" description: "Test results from TestRail, Xray Cloud and Zephyr Scale land in the Qualio trace matrix every hour, each linked to its test case and requirement. Read-only, nothing changes in the tool. For design controls under ISO 13485 and IEC 62304." --- # TestRail, Xray and Zephyr Scale integration for design controls | Qualio Test results from TestRail, Xray Cloud and Zephyr Scale land in the Qualio trace matrix every hour, each linked to its test case and requirement. Read-only, nothing changes in the tool. For design controls under ISO 13485 and IEC 62304. ## Test results land in the trace matrix as they run Qualio reads test cases and results from TestRail, Xray or Zephyr Scale every hour, each result linked to its test and the requirement it covers. ## What Qualio reads from TestRail, Xray and Zephyr Scale Qualio reads the test cases and results from the tool your engineers already use. Each result arrives as passed, failed or blocked, with who ran it and when, and keeps its link to the test case. #### TestRail Test cases with their title, suite, section, references and the steps laid out as a table. The latest result for each test, with who ran it and when. #### Xray Cloud Tests with their steps, Gherkin or plain text, their folder, type and status, plus the Jira summary, labels, components and issue links. Test runs with their status, who executed them, when they finished and the defects raised. #### Zephyr Scale Test cases with their name, key, status, labels, the steps or script laid out as a table and the Jira issues they cover. Executions with their status, who executed them, the comment and the end date. The Jira issues a test covers become its trace links to the requirements from Jira. When a test case changes after its last run, the gap check shows its result as out of date until a new run clears it. ## Connect your test tool in three steps Connect with the key or token below, Xray Cloud and Zephyr Scale once Jira Cloud is connected. Choose the project, and in TestRail the suites and sections. Preview a sample, then Qualio reads it every hour from the moment you save. What your admin creates: - TestRail. API access switched on and a user with a password or API key who can see the project - Xray Cloud. An Xray API key, its client ID and client secret, with the Jira connection already made - Zephyr Scale. A Zephyr Scale access token, with the Jira connection already made ## What the results do once they are in Qualio #### The traceability matrix rebuilds itself on every change Qualio links each result to its test case and each test to the requirement it verifies, and marks a failed, missing or out-of-date result amber before the design review. #### Approve the design review and the documentation generates itself The approvers you name sign the review. On approval Qualio generates the trace matrix, specifications and test plans and exports the package with its change history. ## Where it stops Attachments and evidence files stay in the test tool. Qualio reads the test case and its result from TestRail, Xray and Zephyr and writes nothing back. #### When a token expires When a token expires or is refused, Qualio marks the integration Disconnected, pauses the reads and shows a banner on the Integrations page until someone reconnects it. #### A test case deleted in the tool is marked A test case deleted in the tool is marked deleted in Qualio within about six hours; removing it from the design controls is an approval in Qualio. A deleted result stays, because Qualio does not go back to check that past runs still exist. ## Guides ## Questions about the TestRail, Xray and Zephyr integrations ### Do our test cases or projects have to change? No. Qualio reads the tests as they are, with their steps laid out as a table, from the project you choose and in TestRail the suites and sections. It asks for no particular structure. The engineers keep writing and running tests where they do now. ### We run Jira with Xray or Zephyr. What do we connect? Both. A test in TestRail, Xray or Zephyr that references the Jira key is linked to that requirement in Qualio, so the trace crosses tools without anyone drawing it. Connect Jira first, which gives Qualio the requirements, then Xray Cloud on Jira Cloud, or Zephyr Scale, with its own credential for the tests and runs. The Jira issues a test covers are its links to those requirements. If the Jira connection drops, the test reads pause until it is back. ### How often does it read, and what counts as a new result? Every hour, and the first read runs when you save the connection. After that Qualio picks up what changed since its last read. From TestRail it takes the latest result for each test; from Xray and Zephyr, each run or execution recorded since then. ### What permission does it need? Read access to the project. In TestRail that is a user with API access switched on; in Xray Cloud an API key; in Zephyr Scale an access token. Qualio stores the credential, does not show it again and writes nothing with it. When TestRail asks it to slow down, Qualio waits and tries again. ### Who needs a seat? People who write or approve in Qualio pay: whoever signs the design review or owns the procedures. Everyone who reads or trains is free. An engineer who writes and runs tests in TestRail, Xray or Zephyr needs no seat, because Qualio reads the results in and nobody edits them there. ## Which test result is out of date? See a TestRail, Xray or Zephyr project read into Qualio on the demo: each result on its test case, the out-of-date ones marked, nothing changed in the tool.