Console

Results

Interpret validation outcomes and trends.

Overview

Results interpret case-level pass/fail, duration trends, and failure patterns within completed runs. Each result links to expected vs actual assertions, execution logs, screenshots, and traces where captured.

Use Results with Test Health for flakiness quarantine and Runs comparison for regression analysis across builds.

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

Open run Results tab

Operate → Runs → select run → Results.

Filter by status: failed, passed, skipped.

Drill into failed cases

Open case detail for expected vs actual.

Cross-link to logs and artifacts tabs.

Export or share

Export CSV for analytics pipelines.

Share run URL with reviewers (respect RBAC).

Key concepts

Passed
Case completed; all assertions satisfied within timeout.
Failed
Assertion mismatch, timeout, or environment error.
Skipped
Case excluded by filter, quarantine, or prerequisite failure.

Best practices

  • Validate changes in staging before applying release gates to production.
  • Include run IDs and timestamps when escalating issues to support or auditors.
  • Align internal runbook terminology with Zof Console UI labels for clarity.

Was this page helpful?

Results | Zof AI Documentation