Assert duplicate delivery produces one business effect
A subscription-created event is delivered three times with separate request IDs. The replay should test event-level deduplication rather than merely identical HTTP responses.
- Focused work estimate
- 1h 45m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Idempotency · Integration testing · Business invariants
Estimated field mix
- Quality engineering50%
- Integrations30%
- Distributed systems20%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
An integration team closes incidents with screenshots of provider dashboards, then struggles to reproduce the same delivery sequence. Build a synthetic event corpus and replay runner against an allowlisted local receiver.
Setup prerequisites
- Create a local receiver fixture with an inspectable event store.
- Use generated test signing keys and synthetic payloads only.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- A scenario sends one event identity with three distinct delivery identities.
- The receiver records delivery attempts but creates one subscription effect.
- Changing the event ID while preserving business data follows an explicitly documented business-key policy.
Implementation constraints
- Observe effects through the local receiver inspection API.
Verification to include
- Replay three duplicates and assert delivery and effect counts separately.
- Disable receiver deduplication in a fixture variant and confirm the scenario detects extra effects.
Deliverables
- Duplicate-delivery scenario and effect assertions
Rollout and recovery
Add as the first consumer acceptance scenario; use the same fixture revision when comparing receiver changes.
Value of the work
For the engineer: Practice protocol verification, controlled fault injection, and reproducible incident investigation.
For the team: Review concrete evidence that webhook consumers tolerate real delivery failure patterns.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.