Console
Runs & results
Execution history, run detail, logs, and artifacts.
Overview
Runs are orchestrated execution instances in Zof Console, whether launched manually, on a schedule, from Agent Console, or via CI/CD. Each run captures status, participating cases, timeline of orchestration events, logs, artifacts, and case-level results for triage.
Operate → Runs is the operational hub for execution history. SREs and QA engineers live here during release weeks; executives typically consume summarized outcomes through Reports instead of raw run lists.
Understanding run anatomy prevents misinterpretation: a single failed case may fail an entire run depending on policy; infrastructure errors differ from assertion failures and require different remediation paths.
Who should read this
- QA engineers, SREs, platform teams, and developers operating Zof Console and APIs.
Prerequisites
- Reviewed test cases or suites available for execution
- Application connectivity and agent availability for chosen execution path
When to use this workflow
- Validating a deployment in staging before production promotion
- Investigating regressions after a failed scheduled run
- Gathering artifacts and logs for incident or audit evidence
Run investigation flow
Run investigation flow
From failure signal to actionable fix or quarantine decision.
Step-by-step procedure
Open Operate → Runs
From Console Home, select Operate → Runs or use ⌘K → "Runs".
Apply filters for project, environment, status, and time range to reduce noise.
Copy run ID from detail header when escalating to support.
Start a new run
Choose New run and select project, suite or case scope, and environment explicitly.
Confirm cloud vs endpoint agent routing matches application type.
For pipeline-triggered runs, verify the CI job logged the returned run ID.
Monitor run progress
Watch status transitions: Queued → Running → terminal state (Passed, Failed, Cancelled, Error).
Use timeline tab for orchestration delays versus case execution time.
Cancel only when necessary, document reason for audit trails in regulated environments.
Triage case-level results
Open Tests tab to see per-case outcomes with duration and failure messages.
Compare against last known-good run using comparison controls when available.
Open failing case links to jump to library edit or Test Health cluster.
Collect logs and artifacts
Download logs for engineering analysis; attach screenshots or traces to tickets.
Verify artifact retention policy meets compliance needs before deleting projects.
Redact sensitive data from shared artifacts per your organization policy.
Close the loop
File defects in integrated issue trackers when connectors are configured.
Re-run smoke scope after fixes land in staging.
Update release gate evidence when runs satisfy policy thresholds.
Key concepts
- Queued
- Run accepted, awaiting execution capacity or agent pickup.
- Running
- Validation in progress on one or more agents.
- Failed
- One or more cases failed assertions or policy thresholds.
- Error
- Infrastructure or orchestration fault distinct from test failures.
Best practices
- Name scheduled runs clearly in schedule configuration for searchable history
- Always record run ID in deployment change tickets
- Separate smoke and full regression runs for faster feedback loops
- Treat Error status as platform investigation, Failed as product/test investigation
Common issues
- Run stuck in Queued
- Agent offline, label mismatch, or capacity limits. Check Agent Console fleet and organizational concurrency policy.
- All cases skipped
- Suite filter or environment selector may exclude cases. Verify scope and case platform tags.
Was this page helpful?
