01
Choose
Pick the native reporter or CLI path that matches the test stack.
Platform feature
Connect the test stack you already run to Jira
Use native reporters for supported frameworks or the Testream CLI for custom environments—without redesigning your pipeline.
Last updated July 10, 2026
Direct answer
What is Integrations in Testream?
Testream integrates through native framework reporters and a flexible CLI path. Teams publish structured results from major test stacks and any CI/CD platform that can run a command, while Jira remains the shared delivery surface.
The problem
Integration should be a publishing step, not a migration project
Testream keeps execution in the framework and CI/CD platform your team already operates.
What teams gain
- Use native framework reporters
- Publish CTRF or supported results with the CLI
- Run from GitHub Actions, GitLab CI, Jenkins, Bitbucket, Azure DevOps, and other command-capable pipelines
How it works
A clear path from setup to useful evidence.
02
Configure
Add project credentials and publishing to the existing workflow.
03
Verify
Open the first structured run and its Jira-visible evidence.
Product proof
Native where it matters, flexible everywhere else
Nine documented framework reporters
CTRF and CLI ingestion
CI/CD platform compatibility
Jira-native evidence surfaces
Continue exploring
Related Testream features
Evidence
Automated reporting
Publish automated test results from CI/CD into Jira with run history, failure evidence, artifacts, and release context.
Platform
Artifact storage
Keep screenshots, traces, videos, and logs connected to test results while using your own supported storage configuration.
Evidence
Jira run summaries
Show linked automated test runs, status, commit context, and suite changes directly on the Jira issues your team already follows.