Integrations
Keep your tools. Add independent proof.
The Warden sits above the test-management systems and CI you already run. Their results become evidence for an exact software change, and The Warden records whether the proof is enough. Integration does not require migration. Read-only integrations for AIO Tests, Xray, Zephyr Scale, TestRail and Azure DevOps are being completed and verified for TestWarden’s independent governance workflow. Early-access integration testing is available by arrangement, subject to readiness.
Two different things
Integration is not migration.
The two are separate workflows. You can use either, both or neither.
- Integration
keep your original test-management platform and use its results as verification evidence for The Warden. No test case is moved.
You add a TestWarden subscription alongside AIO Tests, Xray or whichever platform you keep. Pricing is unchanged.
- Migration
optionally import supported test cases into TestWarden’s native Jira repository. Execution history stays in the original tool.
Optional, and CSV-based. See the Migration Center.
Status as of 2026-10-25
What exists for each provider, stated plainly.
Three things are kept apart: whether a report you already have can be submitted, whether connector code exists, and whether anyone has used it live with the vendor’s real service. None of the external provider connectors is released.
- Proven in development
- Exercised in a real Jira Cloud development installation, with real CI runs and disposable data.
- Implemented in source and covered by automated tests. Integration and acceptance are still open.
- Planned
- Not implemented.
- Released
- Available to customers and independently verified. No external provider connector is at this stage today.
| Provider | Report compatibility | Connector code | Live integration |
|---|---|---|---|
| AIO Tests | A complete JUnit XML report produced by your CI is accepted like any other. No provider-specific export has been verified. | Read-only collector for the latest cycle in AIO Tests Cloud, written against the published AIO API. Checks cycle, project and case identities and counts, then writes a JUnit report for the existing Warden gate. | Not run against a real account. No customer connection exists. |
| Xray | A complete JUnit XML report produced by your CI is accepted like any other. No provider-specific export has been verified. | Read-only GraphQL collector for the test runs of a named Test Execution in Xray Cloud. Verifies totals and identities and rejects duplicate or ambiguous attempts. | Not run against a real account. No customer connection exists. |
| Zephyr Scale | A complete JUnit XML report produced by your CI is accepted like any other. No provider-specific export has been verified. | Read-only execution collector for Zephyr Scale Cloud. Requires the vendor’s automated flag, rejects manual or malformed executions and keeps full history. | Not run against a real account. No customer connection exists. |
| TestRail | A complete JUnit XML report produced by your CI is accepted like any other. No provider-specific export has been verified. | Read-only fetch of results from TestRail Cloud, converted to JUnit. Defects found in the latest integrated source are being corrected before acceptance. | Not run against a real account. No customer connection exists. |
| Azure DevOps Test Plans | A complete JUnit XML report produced by your CI is accepted like any other. No provider-specific export has been verified. | Read-only fetch of Test Plans results, converted to JUnit. Defects found in the latest integrated source are being corrected before acceptance. | Not run against a real account. No customer connection exists. |
| GitHub Actions and other CI | Complete JUnit XML, SARIF 2.1.0 or a bounded JSON envelope from any CI job. Real GitHub Actions runs submitted evidence to a TestWarden development installation: a failing build was HELD, and the fixed build was CLEARED with the HELD decision kept in history. | Proven in development A gate script and a reusable GitHub Action wrap the submission and exit zero only for CLEARED on the exact build. The action is a developer preview. | Proven in development only. No customer installation yet. |
Binding a provider’s results to the exact build needs an independent attribution step. That step exists as a verification library in source, but its trusted issuer, key custody and server-side checks are not in place. Until they are, provider-derived evidence is recorded as asserted by CI, and only The Warden’s policy can clear a change.
The provider connectors target the vendors’ cloud products only. Server and Data Center editions are not covered. Evidence from any tool that your CI can export as a complete JUnit XML report is accepted regardless of this table.
Boundaries
What we do not promise.
Early-access integration testing is available by arrangement and subject to readiness. These are not part of it.
- One-click setup. Each connector runs in your CI with read-only credentials that you hold.
- Automatic synchronization. Nothing is kept in step between TestWarden and your test tool.
- Writing back. Connectors read results. They do not create, edit or close anything in your tool.
- Execution-history imports. Past runs stay where they are.
- Endorsement. TestWarden is not partnered with, certified by or endorsed by any provider named here.
The intended workflow
A green result is evidence, not authorization.
Your existing systems keep producing results. The Warden evaluates them independently of their producers and records the decision.
- Evidence producers
- Existing test-management systems
- CI
- Scanners
- Authorized agents
- Evidence ingestion and provenance validation
Each result is tied to an exact repository, commit, build, run and environment, and stored as an immutable receipt.
- Verification Contract and deterministic Warden policy
The contract says what must be proven. A pinned policy interprets the evidence. No model decides.
- The Warden records one decisionHELDNEEDS APPROVALCLEARED
- Where the decision is delivered
- Jira quality record
Changes workspace with decision, reasons and history.
Marketplace V1 — publicly listed - GitHub Check and job summary
Actionable HELD feedback on the pull request.
Developer preview — live acceptance pending - Audit evidence
Immutable receipts and append-only decisions.
Proven in development - Authorized workflow feedback
Developer API, CLI and MCP reads for people and agents.
Developer preview — live acceptance pending
Read how The Warden decides, how to submit CI evidence, or what has been proven so far, or see how TestWarden sits above Harness, SonarQube and JFrog.
Atlassian, Jira and Forge are trademarks of Atlassian Pty Ltd. Xray, Zephyr and AIO Tests are trademarks of their respective owners. TestWarden is not affiliated with, endorsed by or certified by Atlassian or any other vendor named on this site. Names are used only to identify the tools that teams already run.
Now available on Atlassian Marketplace
Proof before progress.
TestWarden is listed on the Atlassian Marketplace for Jira Cloud. Keep your existing test-management and CI tools, and add The Warden's independent verification layer—or use TestWarden's built-in Jira test management. Visit the Marketplace to get started; we're here if you want guided setup or migration help.