Getting Started

Run your first test

Execute validation runs and review operational results.

Overview

Your first validation run confirms end-to-end connectivity between the Console, execution environment, and application under test. Runs produce case-level pass/fail states, orchestration timeline, logs, and optional artifacts (screenshots, traces).

Before running, ensure test cases have been reviewed and approved, the target environment URL is reachable from execution agents, and you know which execution path applies (Console run, cloud agent, or endpoint agent).

Who should read this

  • QA engineers, SREs, platform teams, and developers operating Zof Console and APIs.

Prerequisites

  • Reviewed and approved test cases
  • Application URL accessible from execution environment
  • Appropriate role to trigger runs

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

Confirm readiness

Open the test library or project wizard and verify cases are marked reviewed.

Confirm staging (or target) environment is up and accessible.

Start the run

Navigate to Operate → Runs → New run, or use the project wizard results step.

Select cases or suite, environment, and execution target if prompted.

Monitor execution

Watch run status transition: Queued → Running → Passed/Failed/Error.

Open timeline tab for orchestration events if execution stalls.

Review results

Open the Results tab for case-level outcomes and failure summaries.

Inspect Logs and Artifacts tabs for diagnostics on failed cases.

Document and iterate

File defects in your issue tracker with run ID and artifact links.

Fix application or case issues; rerun failed cases to confirm resolution.

Key concepts

Passed
All critical selected cases completed successfully within policy thresholds.
Failed
One or more cases reported validation failure, inspect case detail, not just run summary.
Error
Infrastructure or orchestration failure, often connectivity, agent offline, or misconfigured environment.

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?

Run your first test | Zof AI Documentation