How-to Guide
Use the Console as a test engineer
Focus on Quality and Operate sections for daily workflows.
Objective
Focus on Quality and Operate sections for daily workflows.
Prerequisites
- Member role
Procedure
Bookmark key areas
Tests, Runs, Specifications, Test Health.
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.
Use command palette
⌘K for fast navigation between workflows.
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.
Follow review discipline
Human review before release-critical execution.
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
Test engineer navigates Console efficiently.
Was this page helpful?
