Overview

End-to-end agents simulate realistic user journeys across authenticated flows, multi-step wizards, and cross-service transactions. They are the primary gate for release readiness when combined with governed human review.

Enable agents per organization in Automation → AI Agents. Human review applies to generated output before release-critical use.

Who should read this

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

Prerequisites

Organization administrator approval to enable agent category
Staging or approved test environment reachable from execution plane
Requirement linkage for audit-oriented teams (recommended)

When to use this workflow

Nightly regression of revenue-critical paths
Pre-production validation before marketing launches
Hotfix verification after production incident

Step-by-step procedure

Define critical journeys

Quality → Scenarios → document top 5-10 business-critical flows.

Link requirement IDs for audit-ready traceability.

Enable E2E agents

Automation → AI Agents → E2E → Enable with browser runtime targets.

Establish release gate

Governance → Release gates → require E2E suite pass on staging.

Integrate with CI via API or CLI for pull-request checks.

Key concepts

e2e validation scope: Multi-page workflows with session persistence; Checkout, onboarding, and account lifecycle flows; Cross-browser critical paths where enabled; Data setup and teardown for repeatable journeys.
Check 1: Multi-page workflows with session persistence
Check 2: Checkout, onboarding, and account lifecycle flows
Check 3: Cross-browser critical paths where enabled

Best practices

Keep suites lean: critical paths over exhaustive UI coverage
Use stable test data fixtures with cleanup hooks
Quarantine flaky cases in Test Health rather than disabling entire suites