Task library REPLAY Quality engineering · Phased project A webhook replay lab for incident recovery 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.
Practice brief · Version 5
Project scope 10 tickets / 3 phases
Total focused work estimate 20h + setup
Suggested stack TypeScript · HTTP · HMAC · SQLite Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included.
Choose a bounded subset for an assessment or practice session. Prerequisites and remaining project work must be agreed separately.
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Pattern topics identify design choices to practice. Read the ticket's acceptance criteria and justify the simplest suitable approach. Tags are not capability or ownership evidence; an untagged ticket has no curated pattern topic assigned.
Recommended next step Start with REPLAY-101 Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
What the engineer takes away Practice protocol verification, controlled fault injection, and reproducible incident investigation.
What the team gains Review concrete evidence that webhook consumers tolerate real delivery failure patterns.
Before you start Create a local receiver fixture with an inspectable event store. Use generated test signing keys and synthetic payloads only. Delivery agreement A synthetic event corpus, safe local replay runner, and repeatable incident scenarios.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.
Delivery phases PHASE 1 Represent exact request bytes and expected receiver effects.
PHASE 2 Control signing, ordering, duplicates, and lost responses.
PHASE 3 Bound replay authority and preserve useful run reports.
Build inspectable event fixtures Represent exact request bytes and expected receiver effects.
REPLAY-101 Entry ticket; project setup still required Estimated field mix
Quality engineering 60% Integrations 20% Security 20% REPLAY-102 Depends on REPLAY-101 Estimated field mix
Quality engineering 50% Security 30% Integrations 20% Reproduce delivery failures Control signing, ordering, duplicates, and lost responses.
REPLAY-103 Depends on REPLAY-102 Estimated field mix
Quality engineering 50% Integrations 30% Distributed systems 20% REPLAY-104 Depends on REPLAY-102 Estimated field mix
Quality engineering 50% Real-time systems 30% Integrations 20% REPLAY-105 Depends on REPLAY-102 Estimated field mix
Quality engineering 60% Security 40% REPLAY-106 Depends on REPLAY-103, REPLAY-104 Estimated field mix
Quality engineering 50% Distributed systems 30% Integrations 20% Make incidents repeatable Bound replay authority and preserve useful run reports.
REPLAY-107 Depends on REPLAY-101 Estimated field mix
Security 60% Quality engineering 20% Networking 20% REPLAY-108 Depends on REPLAY-103 Estimated field mix
Quality engineering 80% Developer tooling 20% REPLAY-109 Depends on REPLAY-106, REPLAY-107 Estimated field mix
Quality engineering 50% Integrations 30% Networking 20% REPLAY-110 Depends on REPLAY-105, REPLAY-108, REPLAY-109 Estimated field mix
Quality engineering 60% Developer tooling 40% Use this project CSV keeps grouping and dependency keys as descriptive fields. Import mapping depends on your tracker configuration.