Scheduling 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%
Domain layer (state machine, conflict detection)	≥ 95%

Test file	What it covers
`test/integration/tenant-isolation.integration.spec.ts`	Appointments/slots never leak across tenants
`test/integration/outbox.integration.spec.ts`	Events written to outbox in same transaction
`test/integration/inbox.integration.spec.ts`	NATS consumed events deduplicated

Scenario	Type	Priority
Book appointment — slot becomes busy	Unit + Integration	Must
Book appointment — slot already busy → 409	Unit	Must
Double-booking blocked (no permission)	Unit	Must
Double-booking allowed (scheduler role)	Unit + Integration	Must
Reschedule — new slot free → old slot released	Integration	Must
Cancel — slot released, waitlist auto-fill triggered	Integration	Must
No-show recording	Unit	Must
Check-in (arrived transition)	Unit	Must
Fulfil (fulfilled transition)	Unit	Must
All invalid transitions rejected	Unit	Must
Optimistic lock conflict on status update	Integration	Must
Waitlist entry created and fulfilled	Integration	Must
Availability search returns only free slots	Integration	Must
Schedule exception blocks slot creation	Unit	Must
Portal bridge: `portal.appointment.requested` creates proposed	Integration	Must
Reminder dispatch — success path	Unit	Should
Reminder dispatch — retry on failure	Unit	Should
Patient deceased event cancels future appointments	Integration	Should
Tenant isolation for appointments	Integration (mandatory)	Must
FHIR Appointment read returns correct status	Unit	Must
HL7 SIU S12 inbound creates appointment	Integration	Should

Contract	Consumer	Pact provider test
`GET /api/v1/appointments/:id`	patient-chart-service	`appointment-by-id.pact.spec.ts`
`appointment.created` event schema	orders-service	`appointment-created.schema.spec.ts`
`appointment.fulfilled` event schema	billing-service	`appointment-fulfilled.schema.spec.ts`