Overview

Regression agents maintain broad functional coverage across previously shipped features, detecting unintended side effects from refactors and dependency upgrades.

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 full regression on staging
Pre-release validation before change window
Post-refactor verification

Step-by-step procedure

Curate regression suite

Quality → Suites → regression tag with prioritized cases.

Review suite size quarterly to prevent runtime creep.

Enable regression agents

Automation → AI Agents → Regression → Enable.

Schedule nightly via Operate → Schedules.

Analyze deltas

Operate → Runs → compare latest nightly vs baseline.

Investigate new failures before promoting release.

Key concepts

regression validation scope: Existing functional cases after code changes; Cross-module workflows affected by shared libraries; Visual and behavioral consistency on high-traffic pages.
Check 1: Existing functional cases after code changes
Check 2: Cross-module workflows affected by shared libraries
Check 3: Visual and behavioral consistency on high-traffic pages

Best practices

Split fast PR regression from comprehensive nightly suites
Link new feature cases to requirements at creation time
Archive obsolete cases instead of leaving dormant noise