Console
Reports
Reliability reports for stakeholders and operational review.
Overview
Reports aggregate execution outcomes for leadership, audit, and release reviews. Scope by project, application, team, and date range. Formats include pass rate trends, failure categories, coverage gaps, and agent utilization summaries.
Scheduled report delivery to email or webhook supports weekly reliability reviews without manual Console exports.
Who should read this
- QA engineers, SREs, platform teams, and developers operating Zof Console and APIs.
When to use this workflow
- Onboarding new team members to Zof terminology and workflows
- Authoring internal runbooks aligned with Console labels
- Designing CI/CD or webhook integrations against documented behavior
Step-by-step procedure
Generate report
Operate → Reports → New report.
Select scope: project, application, or organization.
Define date range aligned to sprint or release window.
Customize sections
Include pass rate, top failures, coverage gaps, and reliability score trend.
Exclude noisy quarantined cases if policy allows.
Share and archive
Export PDF for release readiness meeting.
Store copy in corporate GRC repository for audit trail.
Key concepts
- Organization scope
- All Zof Console and API operations are isolated to your authenticated tenant.
- Governed execution
- Agent output and remediation follow policy packs with human approval when configured.
Best practices
- Standardize report templates per team for comparable sprint reviews
- Attach report links to change tickets for traceability
Was this page helpful?