01 · Choose
Framework and project
Select the test stack and Jira project that will receive evidence.
Automated test management in Jira
Test evidence your whole Jira team can trust.
Connect CI results, reusable BDD specs, and manual test cycles to your Jira releases—so QA, engineering, product, and delivery leaders decide from the same evidence.
Start with one Jira project Keep your existing frameworks Free plan available BYO Cloud
Product view 1 of 3
A complete test run, not a status badge
Test management integrations
Connect the tools you already trust.
Native reporters and the Testream CLI publish structured results. Your existing CI/CD provider runs the command—no pipeline migration required.
Explore integrationsNative reporters and CLI
CI/CD providers
GitHub Actions
GitLab CI
Azure DevOps
Bitbucket Pipelines
Jenkins
CircleCI
Buildkite
Any command-capable CITestream workflow
From source code to release confidence—without a separate QA silo.
02 · Configure
Rovo or manual setup
Use guided setup, a native reporter, or the Testream CLI.
03 · Verify
First ingestion
Confirm the first successful run before the workflow expands.
One verified source · three connected 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 · Jira-native context
Issues and releases
Evidence stays connected to delivery work, behavior, ownership, and versions.
06 · Decision layer
Release Visibility
Inspect gaps, failures, coverage, cycles, and readiness before the ship decision.
Everything you need
One evidence system for automated tests, BDD, manual QA, and releases.
Testream does not ask teams to choose between code-first automation and structured QA. It connects both to the Jira work and releases they already manage.
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
Give every Jira issue a live test signal.
Testream enriches Jira issues with the automated runs connected to that work, so product, QA, and engineering can see whether related tests 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 how test coverage moved with the issue.
BDD coverage
Make acceptance criteria assessable.
BDD Specs and reusable Library behaviors give teams a practical Gherkin layer inside Jira, then compare each behavior against real captured test evidence.
- Draft or improve issue-level specs with Atlassian Rovo.
- Reuse behavior library items across issues, cycles, and releases.
- Review confirmed, likely, or not covered evidence assessments.
Test cycles
Give manual execution a release-ready home.
Test Cycles turn reusable behaviors into lean execution batches, so manual QA results, notes, and uploaded evidence contribute to the same release picture as automated runs.
- Build cycles from existing BDD Library behaviors.
- Record pass, fail, blocked, and skipped outcomes per behavior.
- Link cycles to Jira releases and track progress as evidence changes.
Release confidence
Base release conversations on current test evidence.
When test runs are linked to Jira releases, teams can review readiness from real evidence instead of stale spreadsheets, screenshots, or subjective status updates.
- Review evidence mix, coverage gaps, and readiness state.
- See linked cycles, automated results, and unmapped issues.
- Give release stakeholders a clearer go or no-go signal.
Built for Jira
Jira-native quality evidence, not another disconnected test tool.
Testream brings automated runs, behavior, manual validation, and release signal into the Jira work your delivery team already follows.
Before and after Testream
Stop translating test results by hand.
The product changes the evidence path—not the way engineers write and run tests.
Before
With Testream
BeforeCI logs disappear into pipeline history and Jira gets a copied status
With TestreamDurable automated evidence lands in Jira with failures, artifacts, commits, environments, and run history
BeforeConnecting a reporter and CI workflow depends on generic docs and trial-and-error
With TestreamUse Rovo-assisted or documented setup, then verify the first successful Testream ingestion
BeforeFailure context is rebuilt across CI, chat, screenshots, and Jira
With TestreamInspect errors and artifacts together, then create a Jira issue with the evidence already connected
BeforeAcceptance criteria are copied between issue descriptions and test documents
With TestreamAuthor Jira-native BDD Specs and reuse maintained behavior from the BDD Library
BeforeTeams guess coverage by comparing scenario text with test names
With TestreamVerify BDD behavior against captured evidence with Rovo assistance and reviewer control
BeforeManual QA execution lives in spreadsheets and release notes
With TestreamRun behavior-based Test Cycles with outcomes, notes, uploaded evidence, and release links
BeforeRelease reviews rely on point-in-time status summaries
With TestreamSee Release Visibility, trend movement, coverage gaps, linked cycles, and readiness from current evidence
Project-based pricing
Share quality evidence widely. Pay by Jira project, not by seat.
Save up to 8%
Free
Up to 1 Jira project
$0
per project / month
For one Jira project. No credit card required.
Starter
Up to 3 Jira projects
$9.17
per project / month$10
Billed annually at $329.99/year for up to 3 Jira projects.
Pro
Up to 10 Jira projects
$7.33
per project / month$8
Billed annually at $879.99/year for up to 10 Jira projects.
Enterprise
Up to 20 Jira projects
$6.42
per project / month$7
Billed annually at $1539.99/year for up to 20 Jira projects.
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 signal attached to the work.
Can Testream support manual tests and lightweight QA workflows too?+
Yes. Testream includes reusable BDD Library behaviors and practical Test Cycles as core features, so manual QA evidence, notes, and uploaded files contribute to the same release picture as automated CI results without creating a separate manual test-case system.
Can QA, product, and release teams understand the results?+
Yes. Testream turns raw automated-test output into Jira-native quality context, so non-technical stakeholders do not need to read CI logs to understand risk.
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 brings automated CI evidence, reusable BDD behaviors, and practical Test Cycles into one Jira-native workflow so QA, engineering, and release teams see the same quality picture without duplicating test-case administration.
Start with one real run