After a test run completes, access execution assets in the Last Run Report tab (for the most recent run) or in the Runs tab (for historical runs):
Confirm the symptom:
Open the failing step’s screenshot: check visible state, key text, and URL.
If unclear, scrub the video around the failure time.
Read what happened:
Open Raw Logs on the failing step: look for selector errors, timeouts, JS errors, or network issues.
Check AI Logs for a concise explanation and suggested next actions.
Pinpoint timing or state:
Open Trace: review actions, waits, and network timeline around the failure.
Correlate timestamps between Trace and Raw Logs.
Apply a fix:
Selector: use a more stable attribute or broader strategy.
Timing: replace fixed sleeps with explicit waits (visible, attached, navigation).
Data/flow: update environment variables, test data, or add a prerequisite snippet.
Validate fast:
Use Run From Step to re‑execute from the failing point.
Do a full run when multiple assumptions changed.
Note: In the Editor, the Editor Console at the bottom also displays assets from the last run executed in the editor, providing quick access without leaving the editor view.
