Console

Tests (library)

Browse, organize, and maintain your test inventory.

Overview

The test library is the searchable organizational inventory of scenarios and test cases across projects. It is the system of record for executable validation before runs, schedules, or CI pipelines reference case IDs.

Library maintenance is operational work: merge duplicates, align naming conventions, set priorities, tag platforms, and deprecate obsolete cases. Neglected libraries produce flaky release schedules and ambiguous coverage reports.

Use filters for project, priority, platform, review status, and tags. Power users combine library search with ⌘K jumps to Test Health when investigating failing case histories.

Who should read this

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

Prerequisites

  • At least one project with generated or authored cases
  • Understand difference between scenarios (grouping) and cases (executable units)

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 Quality → Test library

Navigate from left nav or ⌘K → "Test library".

Apply project filter when working within a single initiative.

Switch between scenario and case views depending on whether you are restructuring coverage or editing steps.

Search and filter effectively

Search by requirement ID fragment, case title, or tag (for example smoke, regression).

Filter by review status to find AI-generated drafts awaiting human approval.

Sort by priority when planning smoke suites for deployment pipelines.

Edit case steps and expected outcomes

Open case detail and revise steps where product behavior or selectors changed.

Update expected outcomes to be observable and measurable, avoid subjective-only language.

Save version history mentally: major edits deserve change ticket references for audits.

Organize suites for batch execution

Create or update test suites grouping cases by smoke, regression, or compliance themes.

Keep smoke suites small and fast for pipeline gating; regression suites may run on schedules.

Document suite purpose in description fields for operators unfamiliar with the product.

Coordinate with Test Health

When cases fail repeatedly, locate them in the library to adjust steps or quarantine via Test Health workflows.

Link flaky case remediation tickets to library case IDs for traceability.

Re-enable quarantined cases only after stabilization runs pass in staging.

Prepare library for CI and API consumers

Copy stable case IDs from case detail for pipeline configuration.

Avoid renaming case IDs externally referenced in workflows without coordinated updates.

Publish internal catalogs mapping suite names to case ID lists for service teams.

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

  • Enforce scenario naming: SCN-<REQID>-<short-slug> for traceability
  • Mark review status explicitly, do not rely on informal team knowledge
  • Keep smoke suites under fifteen minutes wall-clock where possible for fast gates
  • Deprecate cases instead of hard delete when runs historically reference them

Common issues

Duplicate cases after regeneration
Merge or deprecate duplicates; tighten requirement linkage to prevent overlapping generation prompts.
Case passes locally but fails in cloud runs
Environment data or URLs differ. Align application environment metadata and test data setup steps.

Was this page helpful?

Tests (library) | Zof AI Documentation