Run Management & Results
Running a test is only half the job. You need to know what happened, why it failed, and whether a fix held. Run Management captures the full execution history so every result is there when you need to investigate or report.
Who it’s for#
QA engineers and release managers who need to track outcomes, diagnose failures, and report on quality.
What it does#
- Execution history — keep a complete record of every run over time.
- Step-by-step results — see each step’s outcome with screenshots and logs attached.
- Rerun failures — re-execute failed tests without rerunning everything.
- AI failure analysis — get a suggested root cause for a failed run (see AI failure analysis).
- Shared results — reports and scorecards read from the same result data across the platform.
How it works#
Each run records its steps with screenshots and logs as it executes. You can rerun just the failures, and request AI failure analysis on a run to suggest a root cause. All of this writes to one shared results store.
Why it matters#
A complete, shared history turns testing from a pass or fail signal into evidence you can act on. When results feed every report and scorecard from one source, the numbers stay consistent wherever you look.