Testing

Requirements & specifications

Upload and structure requirements for governed test generation.

Overview

Requirements are the authoritative input for governed test generation and coverage traceability in autonomous reliability infrastructure. Well-structured requirements reduce review churn, improve scenario naming consistency, and make audit-ready traceability matrices possible.

Teams ingest requirements through project wizards, specification records, or API uploads. Regardless of channel, the quality bar is the same: explicit acceptance criteria, identifiable requirement IDs, and observable outcomes, not narrative prose alone.

Treat requirements as living documents. When product behavior changes, update the specification or project attachment, regenerate or edit affected tests, and refresh coverage before release gates evaluate readiness.

Who should read this

Product managers, business analysts, QA leads, and engineers responsible for requirement authorship and maintenance.

Prerequisites

Access to upload requirements in Projects or Specifications
Agreement on requirement ID format within your product line

When to use this workflow

Authoring new feature requirements before generation
Remediating weak AI output by improving source material
Preparing audit evidence linking requirement IDs to validation

Step-by-step procedure

Adopt a requirement ID scheme

Use stable identifiers such as REQ-PAY-014 embedded in headings and acceptance criteria blocks.

Avoid renumbering IDs mid-release; add superseding notes when behavior replaces older rules.

Mirror IDs in issue trackers and PRDs so Console traceability matches tooling elsewhere.

Write measurable acceptance criteria

Follow Given / When / Then structure for behavioral rules with explicit data constraints.

State observable outcomes, UI states, API status codes, database flags, not internal implementation guesses.

Include negative paths and boundary values (limits, empty states, concurrency) where risk warrants.

Upload or link into Zof Console

Upload during project creation or attach to an existing specification in Quality → Specifications.

Wait for ingestion to complete; do not trigger generation on partially processed documents.

Verify extracted sections in the UI preview when available before proceeding.

Validate generation input quality

Run a pilot generation on a single epic before bulk-uploading an entire PRD.

If scenarios lack requirement references, enrich source text and regenerate targeted sections.

Escalate chronic extraction issues with document format (scanned PDFs) to administrators.

Maintain requirements through change control

Attach change ticket IDs when uploading revised specifications.

Notify project owners to regenerate or manually update dependent cases.

Refresh Coverage matrices after merges to main product branches.

Pair requirements with coverage review

Open Quality → Coverage filtered by requirement ID before release readiness sign-off.

Export gap lists for stakeholders when unmapped requirements represent release risk.

Close gaps via new cases, suite expansion, or explicit risk acceptance documented in governance tools.

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 requirement ID per testable rule, split compound paragraphs
Keep authentication and PII handling requirements explicit for security-oriented test types
Version specifications rather than emailing ad hoc document attachments
Review AI-generated scenarios for invented requirements not present in source text

Common issues

Generated tests do not match product intent: Requirements may be ambiguous or missing edge cases. Tighten acceptance criteria and regenerate; do not only tweak case steps.
Coverage cannot map requirements: IDs missing from specification text or scenario titles. Standardize SCN-<REQID>-* naming during review.

Sample acceptance criteria block

REQ-ORD-008 Order cancellation window
Given an order in "Processing" status created within the last 15 minutes
When the customer submits cancellation with reason code CUST_INIT
Then the order transitions to "Cancelled"
And inventory reservation is released within 60 seconds
And the customer receives confirmation event ORD-CANCEL-OK

Was this page helpful?