Registration Service — Testing Strategy

Status: populated Owner: TBD Last updated: 2026-04-17 Companion: Service Template · TESTING_STANDARDS

1. Coverage Targets

Layer	Target
Global line coverage	≥ 80%
Critical-path files (MPI, merge, vital status)	≥ 90%
Domain layer	≥ 95%

2. Test Types

Type	Framework	Location
Unit	Vitest	test/unit/
Integration	Vitest + testcontainers (Postgres)	test/integration/
Contract (Pact)	Pact.js	test/contract/
E2E	Playwright / Supertest	test/e2e/

3. Mandatory Tests

Test file	What it covers
test/integration/tenant-isolation.integration.spec.ts	Patient rows never leak across tenants; RLS verified
test/integration/outbox.integration.spec.ts	Events written to outbox in same transaction as patient save
test/integration/inbox.integration.spec.ts	Consumed events deduplicated via inbox table

4. Scenario Coverage Matrix

Scenario	Type	Priority
Register patient with all fields	Unit + Integration	Must
Register with only mandatory fields	Unit	Must
Duplicate detection blocks create (score ≥ 85)	Unit + Integration	Must
Unidentified create bypasses 409 block	Unit	Must
Idempotent create replay returns cached 201	Integration	Must
MRN generated correctly per tenant	Unit	Must
Merge — survivorship rules applied	Unit + Integration	Must
Merge — source deactivated, identifiers transferred	Integration	Must
Unmerge — source reactivated	Unit + Integration	Should
Vital status record (deceased)	Unit + Integration	Must
Vital status correction (authorized role)	Unit	Must
Vital status rejected (unauthorized role)	Unit	Must
Encounter create and status machine (all transitions)	Unit + Integration	Must
Invalid encounter transition rejected	Unit	Must
Optimistic lock conflict on patient update	Integration	Must
Patient search: minimum-necessary criteria enforcement	Unit + Integration	Must
Break-glass audit metadata included	Integration	Must
Tenant isolation: cross-tenant patient access blocked	Integration (mandatory)	Must
Portrait upload with consent	Unit + Integration	Should
Portrait denied (clinical display = false)	Unit	Should
Extension schema validation	Unit	Should
Extension payload rejection on schema failure	Unit	Should
FHIR Patient read includes deceased mapping	Unit	Must
FHIR Encounter create maps to internal model	Unit	Must
HL7 ADT A01 inbound creates patient (adapter test)	Integration	Should
Provisional patient reconciliation merge	Integration	Should
Newborn registration with mother linkage	Unit	Should

5. Contract Tests

Contract	Consumer	Pact provider test
GET /api/v1/patients/:id	scheduling-service	patient-by-id.pact.spec.ts
patient.created event schema	orders-service	patient-created.schema.spec.ts
patient.merged event schema	patient-chart-service	patient-merged.schema.spec.ts
FHIR Patient resource	interop-service	fhir-patient.schema.spec.ts