Getting Started

Upload requirements

Ingest specifications and requirements to drive governed test generation.

Overview

Requirements drive governed test generation and coverage traceability. Zof accepts requirements through two primary paths: attachment during project creation, or managed specification records in the Specifications area.

Higher-quality requirements, with numbered acceptance criteria, edge cases, and measurable outcomes, produce more actionable scenarios and cases. Vague bullet lists often require substantial human editing after generation.

Prerequisites

  • Project or specification creation permission
  • Requirements file in a format supported by your service
  • Confirmation of current upload constraints and an approved transfer method

Step-by-step procedure

Choose upload path

Project wizard: attach during Create project for immediate generation context.

Specifications: Platform → Specifications → Add specification for org-wide catalog and traceability.

Prepare the document

Structure requirements with IDs or headings for traceability (REQ-001, US-142).

Include acceptance criteria, error cases, and non-functional requirements where relevant.

Upload and confirm

Drag and drop or browse to select the file; wait for upload confirmation toast.

Verify the document appears in project attachments or specification list.

Link to coverage (Specifications path)

Open Quality → Coverage to map requirement records to generated or authored cases.

Address gaps before release gate evaluation.

Common issues

Upload fails
Check file size and MIME type; retry on stable network; contact admin if storage quota exceeded.
Generation ignores content
Ensure document is attached to the correct project; allow processing time before triggering generation.

Was this page helpful?