Run Detail and Evidence
Open a Test Run to investigate its execution context and persisted evidence. The exact tabs depend on project type, runner, and what the execution produced.
Verify the run header first
Record the run ID and confirm:
- plan and source context;
- status and result;
- start, finish, and duration;
- manual, scheduled, or other trigger;
- Run Profile and environment snapshot; and
- runner or engine attribution.
This prevents evidence from a similarly named or re-run execution being reviewed by mistake.
Scenario and step outcomes
Use the scenario tree and result totals to find failed, errored, untested, or partial work. A plan can finish while some scenarios did not pass, so read both status and result.
Logs, screenshots, and artifacts
Where available, Run Detail can expose:
- timestamped execution events and logs;
- step and scenario attribution;
- captured screenshots;
- browser, mobile, or automation sessions; and
- downloadable artifacts or summaries.
Artifacts are produced by the runner and scenario; their absence is not proof that no failure occurred. Logs can contain target data, URLs, selectors, or values, so handle exports as sensitive test evidence.
Generation detail is different
AI Studio also exposes a generation-run detail and conversation. That record explains how an automation version was generated; it is not the Test Run detail for a plan execution.
Re-run and cancellation
A re-run creates a new execution record. Compare IDs and configuration rather than treating it as an update of the old run. Cancellation may leave partial evidence and may not reverse external actions.
Troubleshooting sequence
- Confirm the final status/result and configuration snapshot.
- Find the first failing or missing scenario.
- Read its events and logs from the earliest error forward.
- Compare screenshots or artifacts with the active automation version.
- Verify runner, target environment, source revision, and test data.
- Re-run only after the cause or diagnostic change is understood.
For aggregate analysis, continue to Reports. To track a defect, use Issue Tracker.
