Console
Console overview
Operate, manage quality, automate, govern, and configure platform settings.
Overview
Zof Console is the operational heart of autonomous reliability infrastructure, not a chat interface or ad hoc script runner. Teams use it to govern how requirements become reviewed tests, how AI testing agents execute under policy, and how results flow into Test Health, coverage, release gates, and reports.
The Console is organized into intentional sections that mirror how enterprise teams work: Home for persona-aware landing; Operate for runs, schedules, and reports; Quality for test health, coverage, scores, the test library, and specifications; Automation for Zof Studio, AI testing agents, and Agent Console; Governance for releases, risk, compliance, security, and remediation; Platform for topology, integrations, applications, and administration.
Developers and pipelines integrate the same capabilities through the REST API, SDKs, and CLI. The Console remains the authoritative surface for human oversight, configuration, and operational triage at scale.
Who should read this
- New Console users, team leads onboarding a department, and technical writers standardizing reliability runbooks.
Prerequisites
- Signed-in access to your Zof organization
- Basic understanding of projects, applications, and validation runs
When to use this workflow
- Onboarding engineers who need a mental model before deep operational work
- Aligning stakeholders on what the Console does versus Agent Console or Zof Studio
- Designing internal runbooks that reference Console section names consistently
Typical reliability loop in the Console
Typical reliability loop in the Console
Most teams iterate through connect → generate → review → execute → analyze → govern, with Console areas supporting each phase.
Step-by-step procedure
Sign in and confirm tenant context
Open the Zof Console and verify the organization name in the top bar matches your intended tenant.
If you belong to multiple organizations, switch tenants before creating projects or starting runs.
Confirm your persona lens (QA, SRE, executive, admin) reflects your primary workflow, adjust in Settings if needed.
Orient to Console sections
Expand the left navigation and note the six section groups: Home, Operate, Quality, Automation, Governance, and Platform.
From Console Home, review persona-specific cards that highlight your highest-priority destinations.
Open the command palette (⌘K on macOS, Ctrl+K on Windows) and search for Operate → Runs to confirm palette navigation works for your role.
Connect your first application
Navigate to Platform → Applications and register the system under test with URL, team ownership, and environment metadata.
For desktop or restricted-network workloads, plan endpoint agent registration in Agent Console before scheduling production validation.
Link the application to an upcoming project so execution targets resolve correctly during runs.
Stand up a project with requirements
Create a project from the project wizard or Projects list, naming the initiative for operational clarity (for example, "Checkout Reliability Q2").
Attach a requirements document or link an existing specification to drive governed test generation.
Select test types aligned to risk, functional, accessibility, security-oriented categories as enabled for your organization.
Review generated tests before execution
Complete scenario and case generation, then edit steps and expected outcomes where AI output needs refinement.
Mark review status explicitly before release-critical runs; treat generated inventory as draft until validated.
Organize approved cases into suites when you plan recurring batch execution or CI triggers.
Execute and monitor a validation run
Start a run from Operate → Runs, the project results step, or an integrated pipeline, choosing environment and case scope.
Monitor run timeline events, agent telemetry, and case-level outcomes until the run reaches a terminal state.
Open run detail tabs for logs and artifacts when triaging failures or documenting evidence for stakeholders.
Analyze health and communicate results
Use Quality → Test Health to cluster failures, quarantine flaky cases, and prioritize stabilization work.
Generate or schedule a report from Operate → Reports for release readiness reviews or executive summaries.
Feed outcomes into release gates and governed remediation when your organization enables those workflows.
Key concepts
- Zof Console
- The full product control plane for reliability operations, not synonymous with Agent Console.
- Agent Console
- A Console area for cloud and endpoint execution agents and their fleet telemetry.
- Operate
- Console section for runs, schedules, and stakeholder reports.
- Quality
- Console section for Test Health, coverage, scores, test library, and specifications.
- Persona lens
- UX emphasis tuned for QA, SRE, executive, compliance, or admin roles.
Best practices
- Use consistent project naming that reflects initiative, application, and time horizon for searchability
- Keep Agent Console agent labels aligned to environment and capability policy to avoid misrouted jobs
- Review AI-generated cases in the library before adding them to release-critical suites
- Bookmark Operate → Runs and Quality → Test Health for on-call runbooks
- Document Console deep links in internal wikis so incident responders skip manual navigation
Was this page helpful?