Tutorial
Review and debug a failed test
Operational tutorial for triaging failed runs with logs and artifacts.
Overview
Operational tutorial for triaging failed runs with logs and artifacts.
Tutorial details
- Audience
- QA engineer
- Duration
- 30 min
- Prerequisites
- Failed run available
Tutorial steps
Open failed run
Runs → select failed run.
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.
Analyze timeline
Review orchestration events and failure point.
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.
Inspect logs and artifacts
Download logs; review screenshots if present.
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.
Compare or rerun
Compare with prior run or rerun after fix.
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.
Expected outcome
Failure root cause identified or documented for escalation.
After completing this tutorial
- Capture run IDs and screenshots for your team runbook
- Share learnings with QA, SRE, or platform stakeholders
- Proceed to related how-to guides for operational hardening
Continue learning
Was this page helpful?
