Skip to content

QA overview

Audience: qa
Status: specced
Owns: QA
Depends on: Lifecycle, Experience flows, Domain entities, Policies

QA validates implemented behaviour against the shared domain language. Prefer cases of the form Given stage/status → When → Then.

Concern Doc
Stages, statuses, close reasons Lifecycle
Invariants Domain entities
Open / proposed rules Policies
Journeys Experience flows
HTTP contract (when available) API overview

See Test cases for the initial acceptance list (happy path, identity, centre dashboard, payments/settings, invite, roster, job postings).

QA tasks use category qa on the delivery board. Completing work should leave corresponding cases updated (pass/fail or blocked with policy ID).