Skip to content

Getting Started

Next steps

Progress to agents, schedules, topology, remediation, and CI integration.

Overview

After your first successful run, mature teams expand along four axes: automation (agents and schedules), integration (CI/CD and webhooks), observability (Test Health, reports, Topology), and governance (release gates and remediation).

The paths below are ordered by typical enterprise adoption, adjust pace based on compliance requirements and team size.

Who should read this

  • QA engineers, SREs, platform teams, and developers operating Zof Console and APIs.

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

Step-by-step procedure

Week 1: Stabilize core workflow

Invite team members and assign roles via Admin Center.

Organize cases into suites for smoke and regression.

Configure notification routing in Settings.

Week 2: Automate execution

Create schedules for nightly regression on staging.

Enable relevant AI testing agents from the catalog.

Register cloud or endpoint agents if desktop or restricted workloads apply.

Week 3: Integrate pipeline

Generate API keys in Admin → Developer.

Add Zof validation step to GitHub Actions, GitLab CI, or Jenkins.

Configure webhooks for run completion notifications.

Month 2: Governance

Configure release gates in Governance → Releases.

Explore Topology for dependency-aware coverage planning.

Evaluate governed remediation workflows if enabled for your organization.

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

  • Validate changes in staging before applying release gates to production.
  • Include run IDs and timestamps when escalating issues to support or auditors.
  • Align internal runbook terminology with Zof Console UI labels for clarity.

Was this page helpful?

01Zof Console

Isang surface para sa posture, operasyon, at kung ano ang kailangang asikasuhin susunod.

Ang authenticated na home na binubuksan araw-araw ng mga team ng engineering, QA, at SRE: quality posture, mga in-flight na run, coverage ayon sa module, at kung ano ang dapat asikasuhin susunod.

OPERATIONAL KPIs

  • Mga Run
  • Coverage
  • Panganib

Live sa bawat environment na sini-ship mo.

WORK SPINE

  • Specs
  • Tests
  • Schedules

Mula sa specification hanggang scheduled regression.

GUARDRAILS

  • RBAC
  • SSO
  • audit

Bawat aksyon ay maiuugnay sa pinangalanang tao.

LIVE/console
Zof AI home command center na nagpapakita ng 12 run sa 94% pass, 3 bukas na kritikal na isyu, 84% coverage, apat na module traceability bar, ang specification pipeline, mga paparating na iskedyul, at mga inirerekomendang susunod na aksyon na may 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

Next steps | Zof AI Documentation