Overview

Smoke agents run fast, shallow validation confirming deploy health: application responds, auth works, core navigation loads, and critical APIs return 2xx. Ideal for post-deploy and hourly health checks.

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

Post-deploy pipeline gate
Hourly production-adjacent staging checks
Rollback trigger after failed smoke

Step-by-step procedure

Define smoke scope

Limit to 5-15 cases with sub-10-minute runtime target.

Map cases to deployment environment tags.

Enable smoke agents

Automation → AI Agents → Smoke → Enable.

Attach smoke suite to Operate → Schedules for hourly runs.

Wire CI gate

Add zof run --suite smoke --wait to deploy pipeline.

Fail deploy job on smoke failure before traffic shift.

Key concepts

smoke validation scope: Application availability and health endpoints; Login and session establishment; Top three navigation destinations load without 5xx; Critical API heartbeat calls.
Check 1: Application availability and health endpoints
Check 2: Login and session establishment
Check 3: Top three navigation destinations load without 5xx

Best practices

Keep smoke independent of heavy data setup
Alert on consecutive smoke failures, not single blips
Review smoke scope after major architecture changes