01
Detect
Open the failed test from the published run or Jira summary.
Evidence feature
Keep every useful clue attached to the failed test
Move from a red CI job to the actual error, artifact, and Jira action without sending teammates through a trail of expired links.
Last updated July 10, 2026
Direct answer
What is Failure inspection in Testream?
Testream Failure Inspection keeps the failed assertion, error output, stack trace, artifacts, run metadata, and Jira follow-up connected so teams can move from detection to useful action without rebuilding context by hand.
The problem
Failure triage slows down when context is split across CI, chat, and Jira
The cost is not finding that a test failed—it is reconstructing enough evidence to understand and act on it.
What teams gain
- Inspect errors and stack traces at test level
- Open screenshots, traces, videos, and logs beside the failure
- Create a Jira issue with evidence already included
How it works
A clear path from setup to useful evidence.
02
Inspect
Review the error, metadata, history, and available artifacts together.
03
Act
Create or connect a Jira issue without rewriting the failure context.
Product proof
Evidence that survives the pipeline job
Errors and stack traces
Screenshots, traces, videos, and logs
Run and environment metadata
Jira issue creation
Continue exploring
Related Testream features
Platform
Artifact storage
Keep screenshots, traces, videos, and logs connected to test results while using your own supported storage configuration.
Delivery
Issue creation
Create actionable Jira issues from failed tests with error output, run metadata, and evidence already attached.
Evidence
Automated reporting
Publish automated test results from CI/CD into Jira with run history, failure evidence, artifacts, and release context.