Getting Started

Create your first project

Create a project, connect an application, and prepare for test generation.

Overview

A project is the central container for reliability work on an initiative. Creating a project connects an application under test, optional requirements, test type selection, AI-assisted generation, human review, execution history, and reporting.

The project wizard guides you through five stages: initial details, test types, scenarios, test cases, and first-run results. Skipping review stages is possible but strongly discouraged for production-bound work.

Who should read this

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

Prerequisites

Active Console session with project creation permission
Application URL reachable from your validation environment
Optional: requirements document (PDF, DOC, DOCX, PNG, JPG)

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 Create project

From Console Home or the project menu, select Create project.

Enter a descriptive name (e.g., "Acme Checkout, Q2 Reliability") and the primary application URL.

Upload requirements (recommended)

Attach a PRD, user story export, or specification document (within documented size limits).

Requirements with explicit acceptance criteria produce significantly better generated tests.

Select test types

Choose categories such as functional, API, accessibility, security, or E2E aligned to your application.

Selection determines which AI agents and generation templates apply.

Review scenarios and cases

Wait for generation to complete; review scenario names and coverage intent.

Edit case steps and expected outcomes; reject or rewrite inadequate cases.

Execute or defer first run

From the wizard results step or Runs, trigger validation against staging.

Record the run ID for troubleshooting reference if execution fails.

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

One project per major initiative or release train, not per individual test case
Link the project to a registered Application record for environment consistency
Document reviewer name and date in your team runbook when approving generated cases

Sample requirement excerpt (paste into your PRD)

Feature: Password reset
As a registered user, I can reset my password via email link within 15 minutes.
Acceptance criteria:
- Reset email arrives within 60 seconds of request
- Link expires after 15 minutes
- Invalid or expired token shows a clear error without revealing account existence
- Successful reset allows login with new password

Was this page helpful?