Overview

Requirements uploads, run artifacts, logs, and reports are stored in encrypted object storage with organization-scoped access controls. Retention periods are configurable for enterprise customers.

Customer application URLs and test data remain customer-controlled; Zof processes validation traffic according to your execution plane (cloud or endpoint).

Who should read this

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

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

Understand upload boundaries

Supported formats: PDF, DOC, DOCX, PNG, JPG within documented size limits.

Uploads attach to projects for requirements traceability.

Configure retention

Admin Center → Platform → Data retention where available on your plan.

Align artifact retention with internal compliance schedules.

Key concepts

Artifacts: Screenshots, traces, HAR exports, and reports generated during runs.
Encryption at rest: AES-256 or equivalent per cloud provider standard for stored objects.

Best practices

Redact PII from requirements documents before upload when possible
Use endpoint agents for applications that cannot expose URLs to cloud execution