01
Collect
Build consistent history from every published run.
Evidence feature
See quality movement before risk becomes a release surprise
Move beyond one green or red run and understand the patterns forming across your automated test history.
Last updated July 10, 2026
Direct answer
What is Trends & analytics in Testream?
Testream Trends and Analytics turns run history into quality movement teams can review by project and release, including pass rate, duration, failure patterns, flaky behavior, and suite growth.
The problem
Point-in-time status hides recurring failures and slow quality drift
Historical signals help teams distinguish an isolated failure from a pattern that needs investment.
What teams gain
- Track pass-rate and duration movement
- Spot recurring and flaky behavior
- Review suite growth beside Jira project and release context
How it works
A clear path from setup to useful evidence.
02
Compare
Review quality signals across time, sources, and releases.
03
Prioritize
Use patterns to guide triage, stabilization, and release work.
Product proof
History that turns status into a decision signal
Pass-rate movement
Duration and performance trends
Recurring and flaky failure patterns
Suite growth context
Continue exploring
Related Testream features
Evidence
Suite changes
See which automated tests were added, removed, or changed between runs and connect suite movement to Jira work.
Delivery
Release visibility
Review automated runs, manual cycles, behavior coverage, and evidence gaps together for clearer Jira release decisions.
Evidence
Automated reporting
Publish automated test results from CI/CD into Jira with run history, failure evidence, artifacts, and release context.