How-to Guide
Debug a failed test
Use logs, timeline, and artifacts to diagnose failures.
Objective
Use logs, timeline, and artifacts to diagnose failures.
Prerequisites
- Failed run with artifacts
Procedure
Open logs tab
Review execution logs and error messages.
Navigation: Console Home quick actions or the project wizard for new initiatives. Use ⌘K / Ctrl+K to jump to any surface.
Verification: Confirm organization and team context in the Console header before making changes.
Inspect artifacts
Check screenshots, traces, or exports if available.
Navigation: Console Home quick actions or the project wizard for new initiatives. Use ⌘K / Ctrl+K to jump to any surface.
Verification: Note project, run, or agent IDs if you may need support escalation.
Compare runs
Use run comparison to identify regressions.
Navigation: Console Home quick actions or the project wizard for new initiatives. Use ⌘K / Ctrl+K to jump to any surface.
Verification: Confirm UI state matches your runbook. Retry once on transient errors before opening a ticket.
Verification checklist
- Confirm expected UI state or API response after each critical step
- Document run ID, project ID, or agent ID for support escalation if needed
- Notify stakeholders if the workflow affects release gates or production validation
Expected result
Root cause identified or escalated with evidence.
Was this page helpful?