What Testream Adds to Jira

Testream is a Jira-native release evidence system. Once a reporter publishes a run, Jira teams can see status, failures, suite changes, release context, reusable BDD behaviors, and issue-level evidence without recreating automated tests as a mirrored manual test-case inventory.

What Jira Gets From Each Run

• Run status where work happens - Dashboard, Test Run Details, and Test Run Summaries in Jira Issues show pass rate, failed tests, branch, commit, and run metadata in Jira.
• Failure evidence attached - Failure Inspection keeps errors, stack traces, screenshots, videos, traces, logs, and metadata connected to the result.
• BDD workflows without duplication - BDD Specs, BDD Library, and Test Cycles help teams draft, reuse, execute, and evidence behaviors inside Jira.
• Run history and release context - Test Suite Changes, Trends & Analytics, Release Management, and Release Visibility show how the suite, runs, cycles, and coverage gaps change across releases.
• Actionable follow-up - Issue Creation turns failed tests into Jira issues with pre-filled context, while PDF Reports provide portable summaries for release reviews.
• Rovo where it removes friction - The Rovo Setup Agent helps teams complete setup, and the BDD Coverage Agent assesses Jira scenarios against captured evidence while reviewers retain control.

Who Uses It

• QA and automation teams monitor test health, inspect failures, and reduce manual test-case maintenance.
• Developers see test evidence for their branches, commits, and CI runs in the Jira context they already use.
• Product, release, and engineering leaders can review run status, coverage gaps, and failure context without digging through CI logs.

Start Here

1. Install Testream for Jira from the Atlassian Marketplace listing.
2. Publish your first run from an existing automated test suite.
3. Use Testream in Jira to inspect runs, review issue summaries, manage BDD workflows, link releases, and export reports.

Next Steps

• Quick Start to prove the first automated run.
• Use Testream in Jira for the in-product workflow after setup.
• BDD Library for reusable behavior management.
• Test Cycles for manual execution on top of reusable behaviors.
• Jira test reporting for the higher-level evaluation path.
• Jira release test management for release-readiness evaluation.
• BDD Jira integration for Gherkin and coverage-evidence workflows.