Overview

AI testing agents are catalog specialists that generate and execute validation for accessibility, API contracts, security surfaces, E2E journeys, load, and more. They operate under organization policy with human review of generated assets before release-critical reliance.

Agents are not a replacement for your entire QA practice; they extend coverage with governed automation aligned to Zof Console labels and API resource names.

Who should read this

New users, technical writers, and integration engineers aligning internal documentation with Zof terminology.

Prerequisites

Basic familiarity with Zof Console navigation
Organization member access

When to use this workflow

Onboarding engineers unfamiliar with Zof terminology
Writing internal runbooks that align with Console UI labels
Mapping customer CMDB or ITSM fields to Zof entities

Step-by-step procedure

Locate in Console

Navigate to Automation → AI Agents.

Use the command palette (⌘K or Ctrl+K) to search for related screens by name.

Use in workflows

Reference this entity when configuring runs, policies, integrations, or reports.

Follow related documentation links below for step-by-step operational procedures.

Verify understanding

Confirm your team uses the same term in Jira/Linear tickets and internal docs.

Escalate terminology questions to your Zof administrator or account team.

Key concepts

AI testing agent: Catalog agent specialized for validation tasks, accessibility, API, security, E2E, and more, enabled per organization.
Where to find it: Automation → AI Agents

Best practices

Match Console UI labels in internal documentation for reduced onboarding friction
Link requirement and test IDs when traceability is required for audits
Do not conflate similar terms (e.g., test run vs test result vs test case)