01 · Run
Existing framework and Jira project
Run the tests where they already live and choose the Jira project that should receive the evidence.
Release evidence for Jira
Know what your Jira release still needs.
Testream connects CI runs, Jira issues, BDD behavior, and focused Test Cycles in one release view. See what passed, what failed, and what still needs validation before you ship.
Keep tests in code Start with one Jira project Reviewer-controlled coverage Project-based pricing
Product view 1 of 3
See what actually ran.
Publish from your existing stack
Keep the frameworks. Publish the evidence.
Native reporters and the Testream CLI send structured results from the CI/CD jobs your team already runs. No pipeline migration required.
See reporter and CLI optionsConnect the evidence behind the release
Publish a run. Connect the context. Review the gaps.
02 · Publish
Reporter, CLI, or Atlassian Rovo setup
Use a native reporter, Testream CLI, or guided Atlassian Rovo setup to publish the first run.
03 · Verify
First captured run
Confirm what Testream received before the team expands the workflow.
One verified source · three evidence paths
04A · Evidence path
Automated runs
Failures, artifacts, commits, environments, suite changes, and trends.
04B · Evidence path
BDD Specs & Library
Rovo-assisted drafting and evidence assessment with reviewer control.
04C · Evidence path
Test Cycles
Pass, fail, blocked, and skipped manual outcomes with notes and files.
05 · Connect
Issues, behaviors, and releases
Keep evidence attached to the Jira work, expected behavior, ownership, and version.
06 · Review
Release Visibility
Inspect failures, coverage, linked cycles, and missing validation before the release review.
A pass rate is only part of the release picture
One release view for runs, behavior coverage, and focused manual checks.
The release review also needs the run, the Jira work, the expected behavior, and the gaps that still need attention in view.
Publish CI test results
Send structured results from the frameworks and pipelines you already run.
Inspect failures and artifacts
Keep errors, stack traces, screenshots, traces, videos, and logs connected.
Track test-suite changes
See which automated tests appeared, disappeared, or changed between runs.
See trends and flaky patterns
Review pass rate, duration, recurring failures, and suite growth over time.
Automated evidence
See what ran on the Jira work.
Testream connects published runs to the Jira issues they support, so product, QA, and engineering can inspect what passed, failed, or changed.
- Run status appears where the work is already tracked.
- Branch and commit context explain where the evidence came from.
- Suite changes show what moved between runs.
BDD behavior
Check whether expected behavior is covered.
BDD Specs and reusable Library behaviors give teams a practical Gherkin layer inside Jira, then compare each behavior with captured test evidence.
- Draft or improve issue-level specs with Atlassian Rovo.
- Reuse behavior library items across issues, cycles, and releases.
- Review the evidence assessment and keep the final decision with the reviewer.
Focused manual validation
Use Test Cycles where automation stops.
Test Cycles turn reusable behaviors into focused checks, so manual outcomes, notes, and uploaded evidence answer the questions a CI run cannot.
- Build cycles from existing BDD Library behaviors.
- Record pass, fail, blocked, and skipped outcomes per behavior.
- Link cycles to Jira releases and keep the result beside automated evidence.
Release review
Find what still needs validation.
When runs are linked to Jira releases, teams can review current evidence instead of stale spreadsheets, screenshots, or subjective status updates.
- Review evidence mix, coverage gaps, and current run state.
- See linked cycles, automated results, and unmapped issues.
- Give release stakeholders the context behind the next action.
Built for automation-led QA
Keep release evidence in Jira, close to the work.
Testream brings automated runs, behavior coverage, focused manual validation, and release gaps into the Jira work your delivery team already follows.
See the workflow in action
Keep the evidence attached to the work.
Testream changes where the evidence is reviewed, not how engineers write and run tests.
Before
With Testream
BeforeCI logs disappear into pipeline history and Jira gets a copied status
With TestreamPublish a durable run with failures, artifacts, commits, environments, and suite changes attached
BeforeConnecting a reporter and CI workflow depends on generic docs and trial-and-error
With TestreamUse a native reporter, the CLI, or guided Rovo setup, then verify the first captured run
BeforeFailure context is rebuilt across CI, chat, screenshots, and Jira
With TestreamInspect the error and artifacts together, then create Jira work with the evidence attached
BeforeAcceptance criteria are copied between issue descriptions and test documents
With TestreamWrite Jira-native BDD Specs and reuse maintained behavior from the BDD Library
BeforeTeams guess coverage by comparing scenario text with test names
With TestreamAssess the behavior against captured evidence and keep the reviewer in control
BeforeManual QA execution lives in spreadsheets and release notes
With TestreamRun focused Test Cycles with outcomes, notes, uploaded evidence, and release links
BeforeRelease reviews rely on point-in-time status summaries
With TestreamReview linked runs, coverage gaps, cycles, and missing validation from current evidence
Project-based pricing
Give every stakeholder access to the same release evidence.
Save up to 14%
Free
Up to 1 Jira project
Evaluate Testream with one Jira project.
$0
per project / month
For one Jira project. No credit card required.
Starter
Up to 3 Jira projects
For small teams bringing automated evidence into Jira.
$9
per project / month$10
Billed annually at $323.99/year for up to 3 Jira projects.
Pro
Up to 10 Jira projects
For growing QA practices working across more projects.
$7
per project / month$8
Billed annually at $839.99/year for up to 10 Jira projects.
Enterprise
Up to 20 Jira projects
For multi-project delivery organizations needing longer history and larger evidence.
$6
per project / month$7
Billed annually at $1439.99/year for up to 20 Jira projects.
Organization
Negotiated project scale
For negotiated project scale, evidence limits, onboarding, and priority support.
Let's talk
Frequently asked questions
The practical questions teams ask before the first run.
Do we need to change how we write tests?+
No. Keep your tests in the frameworks your team already uses. Testream publishes the results into Jira so the evidence becomes easier to find, share, and act on.
Can we start without a big rollout?+
Yes. Start with one Jira project, publish a first automated run locally or from CI, and expand when the team sees the value.
Does Testream replace CI or test frameworks?+
No. CI and test frameworks execute your tests. Testream makes their results visible in Jira, with run evidence, failure context, trends, and release-review context attached to the work.
Can Testream support manual tests and lightweight QA workflows too?+
Yes. Testream includes reusable BDD Library behaviors and focused Test Cycles, so manual outcomes, notes, and uploaded files answer the questions automation cannot answer alone.
Can QA, product, and release teams understand the results?+
Yes. Testream turns raw automated-test output into Jira-native run context, so non-technical stakeholders can review the evidence without reading CI logs.
What happens to screenshots, traces, and logs?+
When your reporter or upload workflow provides artifacts, Testream keeps them connected to the relevant test result and Jira context. Access stays aligned with your Testream and Jira project permissions, so screenshots, traces, and logs are visible to the people who are meant to review them.
How is this different from Xray, Zephyr, or manual test management?+
Those tools are strong when teams need full manual test planning and governance. Testream is different: it keeps CI evidence primary, then adds reusable BDD behavior and focused Test Cycles where they help the release review.
Start with one Jira project