Agent Configuration
Configuration index
Enable by validation area.
Overview
Configure which AI testing agents Zof runs, organized by validation area. Enable coverage aligned to your application risk profile.
Step-by-step procedure
Choose validation areas
Map application risk: start with smoke, regression, and E2E for web apps.
Add security, API, and load coverage based on compliance and scale requirements.
Enable and review
Automation → AI Agents → enable per validation area after admin approval.
Quality → Cases → review generated output before release gates depend on results.
Key concepts
- accessibility
- accessibility validation agents available to enable for your organization.
- api
- api validation agents available to enable for your organization.
- compatibility
- compatibility validation agents available to enable for your organization.
- compliance
- compliance validation agents available to enable for your organization.
- e2e
- e2e validation agents available to enable for your organization.
- endurance
- endurance validation agents available to enable for your organization.
- i18n
- i18n validation agents available to enable for your organization.
- integration
- integration validation agents available to enable for your organization.
- interface
- interface validation agents available to enable for your organization.
- l10n
- l10n validation agents available to enable for your organization.
- load
- load validation agents available to enable for your organization.
- regression
- regression validation agents available to enable for your organization.
- reliability
- reliability validation agents available to enable for your organization.
- sanity
- sanity validation agents available to enable for your organization.
- scalability
- scalability validation agents available to enable for your organization.
- security
- security validation agents available to enable for your organization.
- smoke
- smoke validation agents available to enable for your organization.
- stress
- stress validation agents available to enable for your organization.
- unit
- unit validation agents available to enable for your organization.
Choose validation areas by the failure you need to detect
Map the application’s important failure modes to the validation area that can examine them. Define the observable behavior, input data, execution conditions, and evidence needed before enabling broad coverage.
Review the generated or selected tests with a domain owner and use a controlled negative case to check that the test can detect a meaningful failure. Category labels and agent counts alone do not establish coverage or fitness for a regulated requirement.
Was this page helpful?