Console

Execution

Parallel runs and real-time monitoring.

Overview

Execution orchestrates validation runs across Console triggers, schedules, API, CI, and Agent Console. The execution engine parallelizes case runs, streams progress to Operate → Runs, collects artifacts, and records outcomes for Test Health and release gates.

Execution planes include cloud agents (Zof-managed runtime) and endpoint agents (customer infrastructure). Policy packs govern which agents may target which environments.

Who should read this

  • QA engineers, release managers, and platform teams operating daily validation workflows.

Prerequisites

  • Project with reviewed test cases
  • Enabled agents for selected categories
  • Reachable target environment URL

Execution pipeline

Execution pipeline

From trigger to recorded results

Step-by-step procedure

Trigger run

Operate → Runs → New run, or API POST /v1/runs, or zof run --env staging.

Select environment matching deployment target.

Monitor progress

Runs detail → Timeline tab for case-level status.

Agent Console → agent status view if jobs stall in queued state.

Review outcomes

Results tab for pass/fail breakdown.

Logs and artifacts for failed cases.

Best practices

  • Scope PR runs to smoke or changed-area suites for speed
  • Use Agent Console when cloud egress cannot reach private staging
  • Cancel duplicate runs triggered by webhook retries

Common issues

Runs stuck queued
Execution capacity reached; see /docs/limits/concurrent-runs and Agent Console.
Environment unreachable
Staging URL blocked from cloud agents; use endpoint agents for private networks.
Immediate failure
No cases selected or suite empty; verify project wizard and suite membership.

Was this page helpful?