You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Three repositories have no unit tests (notification-outbox, notification-delivery-log, nip05-verification) #905
Note the trap: test/unit/services/notification-outbox-service.spec.ts exists, but it stubs the repository (claimBatch, markDelivered, markFailed are all sinon stubs) — so the 162 lines of actual SQL in the repository are untested. The user, invoice, event, and invite-code repositories all have specs; these three don't.
How measured
Import graph over the suite: 175 spec files vs 325 src/**/*.ts files — zero spec files reference these three modules (the service spec references the repository only as a stubbed interface).
What's worth covering
Outbox claimBatch semantics: batch claiming without double-delivery across workers
markDelivered / markFailed state transitions and failure-count accounting
Activity