Publish your first automated test run into Jira.
Testream publishes Playwright, Jest, Cypress, JUnit, .NET, Pytest, and other automated test runs into Jira with failure evidence, artifacts, branch and commit context, trends, and release signal.
What every test run gives your Jira team
Jira-native run summaries
See pass rate, failed tests, branch, commit, and suite changes where your team already tracks work.
Failure evidence attached
Keep errors, stack traces, screenshots, traces, videos, logs, and metadata connected to the test result.
History that improves every run
Track trends, flaky behavior, suite growth, and release readiness as automated runs keep landing.
Rovo when it removes friction
Use the Testream Setup Agent for first-run guidance, then Testream BDD Specs for evidence-based coverage review.
From codebase to Jira in one test run
Choose your reporter
Start with Playwright, Jest, Cypress, JUnit, .NET, Pytest, Vitest, WebdriverIO, Mocha, or CLI.
Add your Testream API key
Run locally or configure your Testream API key in CI so Testream can publish results from your existing test command.
Verify the run in Jira
Open your Jira project and confirm the run arrived with status, failures, branch, commit, and evidence attached.
Prove your first Jira-ready test run.
Start with one automated run, then use every run after it to build release confidence with current Jira-native evidence.
Start the Quick Start