01
Publish
Send successive runs from the same project and source.
Evidence feature
See how the automated suite moves with the product
Track added, removed, and changed tests across runs so coverage conversations are based on visible history.
Last updated July 10, 2026
Direct answer
What is Suite changes in Testream?
Testream Test Suite Changes compares published runs so teams can see when tests appear, disappear, or move, giving Jira discussions more context about coverage drift and delivery changes.
The problem
A stable pass rate can hide a shrinking or drifting test suite
Change tracking adds the missing context behind run-to-run quality metrics.
What teams gain
- Compare suite composition across runs
- Spot removed or newly introduced tests
- Connect suite movement to Jira issue context
How it works
A clear path from setup to useful evidence.
02
Compare
Testream identifies suite-level movement between runs.
03
Explain
Use the change history beside Jira work and trend signals.
Product proof
Coverage movement that pass-rate charts cannot show alone
Added and removed tests
Run-to-run suite comparison
Source and issue context
Historical coverage signal
Continue exploring
Related Testream features
Evidence
Trends & analytics
Track pass rate, duration, flaky behavior, failure patterns, and suite growth over time with Jira project context.
Evidence
Jira run summaries
Show linked automated test runs, status, commit context, and suite changes directly on the Jira issues your team already follows.
Evidence
Automated reporting
Publish automated test results from CI/CD into Jira with run history, failure evidence, artifacts, and release context.