Product
Keep your tools. Add an independent verdict. Native testing, too.
Add The Warden above the test-management systems and CI you already run, and let it decide whether the combined proof for an exact build is enough. Want native test management as well? Shared tests, cycles, version-pinned attempts, defects and coverage are included in the same Jira app.
Two ways to use TestWarden
Choose the path that fits your stack.
Both paths are first-class. They use the same Warden, the same evidence model and the same Jira app, and teams can start with one and add the other later. Migration is optional.
- Path 1
Keep your tests. Add The Warden above them.
Your test-management system, CI, scanners and authorized agents keep running exactly as they do today. Their results become evidence. The Warden checks that evidence against a verification contract for the exact change and decides whether there is enough proof to proceed. You add a TestWarden subscription; nothing is retired.
- Path 2
Want native test management? It is built in.
TestWarden for Jira also includes a shared test repository, cycles, version-pinned execution, requirement coverage and an optional Migration Center for Xray, Zephyr Scale and CSV exports. Migration is a choice, never a requirement for using The Warden.
Integration: keep your original test-management platform and use its results as verification evidence for The Warden. No test case is moved.
Migration: optionally import supported test cases into TestWarden’s native Jira repository. Execution history stays in the original tool.
Provider status is on Integrations. Read how The Warden decides, or compare TestWarden with Xray, Zephyr Scale and AIO Tests. The Warden decides on automated CI evidence; recorded manual executions are not yet inputs to its decisions.
Workspaces
Six workspaces, one source of truth.
The product navigation as it ships: Changes, Repository, Plans & Runs, Verification, Migration and Evidence Sources.
- 01
Changes
The default workspace. See what changed, what proof arrived and what still needs attention. Every Change Set shows its Warden state, contract and policy version, evidence received, reasons, next actions and decision history.
- 02
Repository
Shared Library and Project Tests with folders, tags, owners, priority, status, quick views, saved filters and bulk actions. Indexed cursor pagination keeps large libraries fast.
- 03
Plans & Runs
Test cycles with release and environment context. Compose from a folder, saved view or tag; hold up to 500 canonical tests per cycle without copying them.
- 04
Verification
Requirement lookup shows linked tests and latest execution state for any Jira issue. Release coverage shows execution completeness, failing and blocked tests, and untested requirements.
- 05
Migration (optional)
Move from Xray Test Case Importer CSV, Zephyr Scale CSV or Generic CSV (including AIO Tests data exported as CSV) through upload, mapping, preview and validation, background import and a per-row fidelity report.
- 06
Evidence Sources
What The Warden accepts — JUnit XML, SARIF 2.1.0 and Generic JSON over the authenticated App REST API — and which producers have submitted accepted evidence.
Repository
A shared test library, not a pile of copies.
Tests live once in the Shared Library and are associated with the Jira projects that need them. Folders, tags, ownership, priorities and saved filters organise the library without duplicating it.
| Test case | Priority | Status | Owner | Updated | |
|---|---|---|---|---|---|
Refund is issued for a partially shipped order TW-3F9A12BC · v5 · checkout, refunds · Projects: PAY, WEB | High | MK | 2h ago | ||
Customer can change delivery address before dispatch TW-7C21E0A4 · v3 · fulfilment · Projects: WEB | Medium | JS | Yesterday | ||
Promotion code is rejected after expiry date TW-A91D44F0 · v2 · promotions, regression · Projects: PAY, WEB, MOB | Critical | MK | 3d ago | ||
Saved card is removed from wallet TW-0E5B77D2 · v1 · wallet · Projects: MOB | Low | Unassigned | 5d ago | ||
Order confirmation email lists every line item TW-C4D80A19 · v4 · notifications · Projects: WEB | Medium | AR | 1w ago |
Authoring
Author once. Preserve what every attempt actually tested.
- Title and description / preconditions
- One focused editing surface with autosave 1.2 s after edits, undo/redo for draft fields and explicit Save now.
- Priority and status
- Low, Medium, High, Critical. Draft or Ready.
- Structured steps
- Action, test data and expected result per step. Insert below, duplicate, reorder, delete, or paste up to 100 steps at once.
- Projects and requirements
- Associate a shared test with any Jira project. Link Jira issues as requirements to drive zero-config coverage.
- Version history
- Every change is an immutable snapshot. Executions pin the test version they ran against.
- Archive and restore
- Meaningful QA records are archived, never hard-deleted, and can be restored.
- Not Run1.Place an order for two items; ship only the firstExpected: Order shows one shipped and one pending line
- Not Run2.Open the order and choose Refund → Partial amountExpected: Refund dialog lists only the unshipped line
- Not Run3.Enter the pending line amount and confirmExpected: Refund is issued; order total updates
- Not Run4.Reload the order pageExpected: Refund appears in the payment timeline with reference
Execution runner: step outcomes Passed, Failed, Blocked, Skipped and Not Run; keyboard shortcuts P / F / B / S; Jira Bug creation from a failed or blocked step with cycle, release, environment and attempt auto-filled.
Changes and Evidence Sources
The verification layer lives in the same app.
Send CI evidence through the App REST API and every change appears in the Changes workspace with its Warden state, the proof received, the reason and the full decision history.
- JUnit XML — complete test-run reports from CI.
- SARIF 2.1.0 — static-analysis and security results from scanners.
- Generic JSON — 1–20 bounded observations from CI, scanners, code reviewers, autonomous agents or visual agents.
Each submission is limited to 256 KiB and must name the exact repository, commit, build and environment it verifies. A source's own pass, approval or score never clears a change.
Built for enterprise review
Tenant-isolated, Forge-hosted and auditable by design.
Architecture facts, not certifications: TestWarden does not claim SOC 2, ISO 27001 or similar attestations. Optional AI explanation is a separate, admin-enabled capability described on the Security page.
Tenant isolation
Installation identity comes from Forge runtime context, and every row carries it.
Forge-hosted
Compute, SQL and object storage run on Atlassian Forge. The submitted version declares no external egress.
Declared scopes
Two Jira scopes, the personal-data reporting scope and two app-defined API scopes. Details on the Security page.
Audit trail
Receipts are immutable and Quality Decisions are append-only, each pinned to contract, policy and engine version.
See the full security and trust overview, or what is proven so far.
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.