How-to Guide

Rerun a failed test

Re-execute a failed validation after fixes or environment correction.

Objective

Re-execute a failed validation after fixes or environment correction.

Prerequisites

  • Prior failed run exists

Procedure

Open failed run

Navigate to Runs and open the failed run detail.

Navigation: Operate → Runs, Reports, or Schedules. Filter by project in large tenants to reduce noise.

Verification: Confirm organization and team context in the Console header before making changes.

Analyze failure

Review logs, artifacts, and case outcomes.

Navigation: Operate → Runs, Reports, or Schedules. Filter by project in large tenants to reduce noise.

Verification: Note project, run, or agent IDs if you may need support escalation.

Rerun

Trigger rerun for failed cases or full run.

Navigation: Operate → Runs, Reports, or Schedules. Filter by project in large tenants to reduce noise.

Verification: Confirm UI state matches your runbook. Retry once on transient errors before opening a ticket.

Verification checklist

  • Confirm expected UI state or API response after each critical step
  • Document run ID, project ID, or agent ID for support escalation if needed
  • Notify stakeholders if the workflow affects release gates or production validation

Expected result

New run reflects updated application state.

Was this page helpful?

01The operational surface

One surface for posture, operations, and what needs attention next.

The Zof home is not a marketing dashboard. It is the operational surface engineering, QA, and SRE teams use every day, quality posture, in-flight runs, coverage by module, and the actions a leader should look at next.

OPERATIONAL KPIs

  • Runs
  • Coverage
  • Risk

Live across every environment you ship to.

WORK SPINE

  • Specs
  • Tests
  • Schedules

From specification to scheduled regression.

GUARDRAILS

  • RBAC
  • SSO
  • audit

Every action attributable to a named human.

STAGING · LIVE/home
Zof AI home command center showing 12 runs at 94% pass, 3 open critical issues, 84% coverage, four module traceability bars, the specification pipeline, upcoming schedules, and recommended next actions with an active-runs sidebar.
Home view · Checkout Service · Staging · captured live from the product.
  • 01 · RUNS · 24H

    94% pass

    12 runs across staging

  • 02 · COVERAGE

    84%

    Across four modules

  • 03 · ACTIVE RUNS

    3 running

    Live on this branch

  • 04 · NEXT ACTIONS

    Recommended

    Triage gaps, new spec

Rerun a failed test | Zof AI Documentation