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

When to use this workflow

  • Onboarding new team members to Zof terminology and workflows
  • Authoring internal runbooks aligned with Console labels
  • Designing CI/CD or webhook integrations against documented behavior

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 → fleet view if jobs stall in queued state.

Review outcomes

Results tab for pass/fail breakdown.

Logs and artifacts for failed cases.

Key concepts

Organization scope
All Zof Console and API operations are isolated to your authenticated tenant.
Governed execution
Agent output and remediation follow policy packs with human approval when configured.

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
Fleet at capacity; 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?

01The operational surface

One surface for posture, operations, and what needs attention next.

The Zof home is not a marketing dashboard. It is the operational surface engineering, QA, and SRE teams use every day, quality posture, in-flight runs, coverage by module, and the actions a leader should look at next.

OPERATIONAL KPIs

  • Runs
  • Coverage
  • Risk

Live across every environment you ship to.

WORK SPINE

  • Specs
  • Tests
  • Schedules

From specification to scheduled regression.

GUARDRAILS

  • RBAC
  • SSO
  • audit

Every action attributable to a named human.

STAGING · LIVE/home
Zof AI home command center showing 12 runs at 94% pass, 3 open critical issues, 84% coverage, four module traceability bars, the specification pipeline, upcoming schedules, and recommended next actions with an active-runs sidebar.
Home view · Checkout Service · Staging · captured live from the product.
  • 01 · RUNS · 24H

    94% pass

    12 runs across staging

  • 02 · COVERAGE

    84%

    Across four modules

  • 03 · ACTIVE RUNS

    3 running

    Live on this branch

  • 04 · NEXT ACTIONS

    Recommended

    Triage gaps, new spec

Execution | Zof AI Documentation