Testing History stores evidence from completed and previous testing runs.
What history can contain
A saved run can include:
- Instance
- Test
- Status
- Start time
- Duration
- Step status
- Step duration
- Failure details
- Screenshots
- Comparison screenshots
- Diff screenshots
- Visual difference percentage
Review a run
- Open Testing History.
- Find the appropriate run.
- Open its detail view.
- Review the overall outcome.
- Inspect failed steps.
- Review screenshots and diffs.
- Compare with earlier runs when necessary.
What to investigate first
Prioritize:
- Fatal or availability failures.
- Authentication/admin failures.
- Critical functional failures.
- Missing assets.
- Unexpected visual changes.
- Slow steps.
Before-and-after comparison
History is most useful when both a baseline and a post-change run exist.
Compare:
- Tests selected
- Environment
- Failures
- Durations
- Screenshots
- Visual diffs
Using history for release decisions
A successful run is evidence, not an absolute guarantee.
Consider:
- Whether the correct tests were selected.
- Whether critical business workflows were covered.
- Whether warnings were reviewed.
- Whether external integrations were realistically represented.
Troubleshooting old failures
Historical evidence lets you determine whether a newly noticed problem actually began with the latest update.
Look for the earliest run showing the same failure.