Overview

Getting started with Zof means establishing an organization context, creating a project, ingesting requirements, reviewing AI-assisted tests, executing validation runs, and expanding into agents, schedules, and governance workflows.

Enterprise onboarding typically spans three phases: (1) account and organization setup, (2) first project and run within a week, (3) CI integration and release gates within a month. This section documents phase one and two in detail.

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

Create or join an organization

Register with corporate email or accept an invitation.

Complete organization onboarding if prompted.

Create your first project

Connect an application URL and optional requirements document.

Select test types aligned to your risk profile.

Review generated tests

Validate scenarios and cases before execution.

Edit steps and expected outcomes where AI output is imprecise.

Run and review results

Trigger a run from Runs or the project wizard.

Inspect logs, artifacts, and case outcomes.

Expand operations

Enable agents, configure schedules, explore Topology and release gates.

Integrate API or CI/CD for pipeline-triggered validation.

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.