Skip to content
Documentation

How Zof Works

Get up and running in minutes. Here's your step-by-step guide.

01

Connect Your Repository

Connect your GitHub, GitLab, or Bitbucket repository. Our AI will analyze your codebase to understand your application structure.

  • One-click OAuth connection
  • Works with public and private repos
  • Automatic branch detection
02

Select Test Types

Choose from 19 verification domains. Zof generates the right verification for your application.

  • Agent-based test generation
  • Natural language test creation
  • Import existing tests
03

Configure & Customize

Fine-tune test parameters, set up environments, and configure CI/CD integration for automated testing.

  • Multiple environment support
  • Custom assertions
  • Parallel execution
04

Run & Monitor

Execute tests on-demand or automatically on every commit. Get real-time results and detailed analytics.

  • Real-time execution logs
  • Video recordings
  • Slack/Teams notifications
05

Self-healing validation

When your UI changes, our AI automatically updates tests to match. No more broken tests from minor changes.

  • Automatic selector updates
  • Smart element detection
  • Change notifications
or explore with a free trial
Next step

Ready to Start Testing?

Follow the guide and have your first tests running in minutes.

01System Graph

Understand the consequence of every change.

The System Graph continuously models services, APIs, dependencies, infrastructure, agents, models, policies, evidence, ownership, and history, so Zof knows what a proposed action could affect before it is allowed to happen.

CONSEQUENCE

Blast radius

Affected systems, criticality, and controls resolved per change.

TEMPORAL

What changed, when, by whom

History, evidence, and decisions stay queryable.

SUBSTRATE

One graph, whole loop

Verification, evidence, and control read the same model.

MAPPED · LIVE/system-graph
Schematic of the Zof System Graph resolving a change to auth-service: Payment API, Checkout, Ledger, and Customer API highlighted as affected, with a readout showing Tier 0 criticality, 7 affected systems, 4 applicable controls, 2 historical incidents, and 6 required verifications.
System Graph · schematic showing the potential impact of a change.